<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7652.24">
<TITLE>RE: [PATCH] [POWERPC] Xilinx: add compatibility for 'simple-bus'.</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<BR>
<P><FONT SIZE=2>Is there really much of a chance of that, given the differences with the bootwrappers?<BR>
Does anyone care enough about legacy_serial for this to matter? My impression was that legacy serial was not preferred anyway...<BR>
<BR>
Steve<BR>
<BR>
-----Original Message-----<BR>
From: glikely@secretlab.ca on behalf of Grant Likely<BR>
Sent: Sat 6/28/2008 1:33 PM<BR>
To: Stephen Neuendorffer<BR>
Cc: dwg@au1.ibm.com; jwboyer@linux.vnet.ibm.com; linuxppc-dev@ozlabs.org; git<BR>
Subject: Re: [PATCH] [POWERPC] Xilinx: add compatibility for 'simple-bus'.<BR>
<BR>
On Fri, Jun 6, 2008 at 10:16 AM, Stephen Neuendorffer<BR>
<stephen.neuendorffer@xilinx.com> wrote:<BR>
><BR>
> legacy_serial identifies a valid ns16550 on a simple-bus, but the<BR>
> legacy_serial driver doesn't understand the shift and offset flags<BR>
> necessary to get it to work, which results in no console.<BR>
><BR>
> I think the easiest solution is to change the Kconfig so that<BR>
> PPC_UDBG_16550 is only selected based on !XILINX_VIRTEX. I've done this<BR>
> in my tree, but I've been swamped with other things at the moment, so I<BR>
> haven't verified it.<BR>
<BR>
This is an easy solution, but it is not a good one. Doing so would<BR>
break UDBG on other 405 boards when building multiplatform kernels.<BR>
It would be better to teach legacy serial about the shift and offset.<BR>
Alternately, add code to add_legacy_soc_port() to skip it if the<BR>
shift/offset properties are present.<BR>
<BR>
Cheers,<BR>
g.<BR>
<BR>
--<BR>
Grant Likely, B.Sc., P.Eng.<BR>
Secret Lab Technologies Ltd.<BR>
<BR>
<BR>
</FONT>
</P>
<br clear=all> This email and any attachments are intended for the sole use of the named recipient(s) and contain(s) confidential information that may be proprietary, privileged or copyrighted under applicable law. If you are not the intended recipient, do not read, copy, or forward this email message or any attachments. Delete this email message and any attachments immediately.
</BODY>
</HTML>