From: "Grant Likely" <grant.likely@secretlab.ca>
To: "David H. Lynch Jr." <dhlii@dlasys.net>
Cc: linuxppc-embedded <linuxppc-embedded@ozlabs.org>
Subject: Re: virtex_devices.c
Date: Sun, 6 May 2007 19:17:37 -0600 [thread overview]
Message-ID: <528646bc0705061817h7a8fd767v73195e9d4572b8e1@mail.gmail.com> (raw)
In-Reply-To: <528646bc0705061746s28ebb15et428c7afda2f477ba@mail.gmail.com>
On 5/6/07, Grant Likely <grant.likely@secretlab.ca> wrote:
> On 5/6/07, David H. Lynch Jr. <dhlii@dlasys.net> wrote:
> > The basic fundimental question is why is there an 8250 specific
> > structure,
> > when there is a perfectly good generic structure that already exists ?
> > Actually it seems to be even more complex than that because I think
> > there is actually an
> > old_serial structure that is also used in places.
>
> I ask the opposite question; why try to make the 8250 structure
> generic when there is already a generic structure that does exactly
> what you want one level up?
>
> I *do* think that 8250 should be changed; but not in the way you're describing.
Although this point is actually moot because platform_bus pretty much
goes away when we move to arch/powerpc. We'll be using
of_platform_devices instead (which map onto nodes in the device tree).
Cheers,
g.
--
Grant Likely, B.Sc. P.Eng.
Secret Lab Technologies Ltd.
grant.likely@secretlab.ca
(403) 399-0195
next prev parent reply other threads:[~2007-05-07 1:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <463C379D.7020804@dlasys.net>
2007-05-05 22:16 ` virtex_devices.c Grant Likely
2007-05-06 21:39 ` virtex_devices.c David H. Lynch Jr.
2007-05-07 0:46 ` virtex_devices.c Grant Likely
2007-05-07 1:17 ` Grant Likely [this message]
2007-05-07 6:38 ` virtex_devices.c David H. Lynch Jr.
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=528646bc0705061817h7a8fd767v73195e9d4572b8e1@mail.gmail.com \
--to=grant.likely@secretlab.ca \
--cc=dhlii@dlasys.net \
--cc=linuxppc-embedded@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).