linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Grant Likely <grant.likely@secretlab.ca>
To: Stephen Neuendorffer <stephen.neuendorffer@xilinx.com>
Cc: John Linn <linnj@xilinx.com>, Alon Ziv <alonz@discretix.com>,
	linuxppc-dev@lists.ozlabs.org, Arnd Bergmann <arnd@arndb.de>
Subject: Re: Bug in drivers/serial/of_serial.c?
Date: Fri, 20 Nov 2009 14:58:24 -0700	[thread overview]
Message-ID: <fa686aa40911201358n5e5eb871wbfa523bfc9adb59d@mail.gmail.com> (raw)
In-Reply-To: <a1cde516-ea22-4411-bae1-74878f6bee43@SG2EHSMHS002.ehs.local>

On Thu, Nov 19, 2009 at 10:42 AM, Stephen Neuendorffer
<stephen.neuendorffer@xilinx.com> wrote:
>
>
>> -----Original Message-----
>> From: linuxppc-dev-bounces+stephen=3Dneuendorffer.name@lists.ozlabs.org
> [mailto:linuxppc-dev-
>> bounces+stephen=3Dneuendorffer.name@lists.ozlabs.org] On Behalf Of Arnd
> Bergmann
>> Sent: Thursday, November 19, 2009 9:33 AM
>> To: Stephen Neuendorffer
>> Cc: John Linn; Alon Ziv; linuxppc-dev@lists.ozlabs.org
>> Subject: Re: Bug in drivers/serial/of_serial.c?
>>
>> On Thursday 19 November 2009, Stephen Neuendorffer wrote:
>> > If the problem is in the device trees that are being generated, we
>> > should fix the issue there.
>> > We've been trying to avoid putting the fully specified IP versions
> in
>> > the kernel like this, since
>> > the IP changes so often.
>>
>> No, the problem that Alon has is that the firmware currently has no
>> way whatsoever to give a correct device tree, because of-serial.c
>> does not even know about ns16550a.
>>
>> The patch adds both a special-case for the specific uart he
>> is using so that one is grandfathered in and a new compatible
>> value so future boards can specify both ns16550a and ns16550.
>
> That's true... =A0The 16550a line still needs to get added, but not the
> xlnx-
> specific line.

The xlnx- line should be added and is entirely appropriate for exactly
the reason Arnd stated.

g.

--=20
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.

  reply	other threads:[~2009-11-20 21:58 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-15  9:30 Bug in drivers/serial/of_serial.c? Alon Ziv
2009-11-16  8:09 ` Arnd Bergmann
2009-11-19 12:47   ` Alon Ziv
2009-11-19 13:01     ` Arnd Bergmann
2009-11-19 13:32       ` Alon Ziv
2009-11-19 13:41         ` Arnd Bergmann
2009-11-19 13:49           ` Alon Ziv
2009-11-19 14:09             ` Arnd Bergmann
2009-11-19 16:03               ` Greg KH
2009-11-19 17:22             ` Stephen Neuendorffer
2009-11-19 17:33               ` Arnd Bergmann
2009-11-19 17:42                 ` Stephen Neuendorffer
2009-11-20 21:58                   ` Grant Likely [this message]
2009-11-20 22:11                     ` John Linn
2009-11-21  7:51                       ` Grant Likely
2009-11-21 19:45                         ` Arnd Bergmann
2009-11-22 22:42                           ` Grant Likely
2009-11-22 22:43                             ` Grant Likely
2009-11-20 21:56               ` Grant Likely
     [not found]             ` <977C41F842E66D4CB2E41332313B615008FC3C2F@XSJ-EXCHVS1.xlnx.xilinx.com>
2009-11-19 17:36               ` John Linn
2009-11-19 17:20     ` Stephen Neuendorffer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=fa686aa40911201358n5e5eb871wbfa523bfc9adb59d@mail.gmail.com \
    --to=grant.likely@secretlab.ca \
    --cc=alonz@discretix.com \
    --cc=arnd@arndb.de \
    --cc=linnj@xilinx.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=stephen.neuendorffer@xilinx.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).