From: Jon Loeliger <jdl@jdl.com>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: linuxppc-dev@ozlabs.org, linux-serial@vger.kernel.org,
Arnd Bergmann <arnd@arndb.de>
Subject: Re: 8250.c::autoconfig() fails loopback test on MPC824[15]
Date: Sun, 05 Aug 2007 16:50:29 -0500 [thread overview]
Message-ID: <E1IHnzZ-0008SZ-2y@jdl.com> (raw)
In-Reply-To: Your message of "Sun, 05 Aug 2007 23:39:19 +0200." <Pine.LNX.4.60.0708052336360.4120@poirot.grange>
So, like, the other day Guennadi Liakhovetski mumbled:
> On Sun, 5 Aug 2007, Jon Loeliger wrote:
>
> ...if you choose to use of_serial.c, yes, if you don't use it and just use
> legacy_serial.c, then you're fine.
Ah, I see. OK.
> BTW, my offer still holds to see if we can build a single kernel for both
> with just specific device-trees, but that's a separate matter:-)
Indeed. I'm fully on-board with that goal, but it may take a couple
rounds to refine it into that state.
One question I have is the stupid ethernet driver. Is the driver
that is in mainline now usable on the StorCenter? I haven't
waded through the supplied vendor patch to verify how it compares
to the r8169 in mainline yet.
Also, what do you want to do about the Kconfig set up for these then?
Specifically, do you want to have "TurboStation" and "StorCenter"?
Or would it make more sense to have something like a generic
"NAS8241" with sub-choices of "storcenter" and "turbostation"?
Thanks,
jdl
next prev parent reply other threads:[~2007-08-05 21:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-04 23:17 8250.c::autoconfig() fails loopback test on MPC824[15] Guennadi Liakhovetski
2007-08-04 23:35 ` Arnd Bergmann
2007-08-05 14:06 ` Guennadi Liakhovetski
2007-08-05 16:41 ` Arnd Bergmann
2007-08-05 21:31 ` Jon Loeliger
2007-08-05 21:39 ` Guennadi Liakhovetski
2007-08-05 21:50 ` Jon Loeliger [this message]
2007-08-05 21:57 ` Arnd Bergmann
2007-08-06 19:29 ` Segher Boessenkool
2007-08-06 19:54 ` Guennadi Liakhovetski
2007-08-06 19:15 ` Segher Boessenkool
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=E1IHnzZ-0008SZ-2y@jdl.com \
--to=jdl@jdl.com \
--cc=arnd@arndb.de \
--cc=g.liakhovetski@gmx.de \
--cc=linux-serial@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
/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).