From: "Mark Chambers" <markc@mail.com>
To: "Pantelis Antoniou" <panto@intracom.gr>,
"Robert P. J. Day" <rpjday@mindspring.com>
Cc: "Embedded Linux PPC list" <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: random ramblings on 8xx patches (long and tedious :-)
Date: Fri, 23 Jul 2004 11:56:07 -0400 [thread overview]
Message-ID: <00a601c470cd$94f5cd80$0301a8c0@chuck2> (raw)
In-Reply-To: 410123EE.4000602@intracom.gr
> The family should be sufficient (say 8xx).
>
> Then everything should be automatically set up at run-time, based
> on probing code which should detect the rest.
>
> That's what OCP should do ideally when it is ready.
>
> In this day and age wasting 50k to kill every-single last
> ugly define in drivers or the setup code is worth it; again IMHO.
>
This sounds like a good idea, especially since the setup code can probably
be thrown away after startup. However, does this fully solve the problem?
For instance if the user is deciding whether to include a UART or USB driver
for SCC3 doesn't he needs to know at that time whether it's on chip or not?
Perhaps udev handles this situation?
Mark Chambers
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-07-23 15:56 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-22 12:00 random ramblings on 8xx patches (long and tedious :-) Robert P. J. Day
2004-07-22 17:46 ` Matt Porter
2004-07-23 12:34 ` Robert P. J. Day
2004-07-23 13:36 ` Wolfgang Denk
2004-07-23 14:09 ` Robert P. J. Day
2004-07-23 14:56 ` Wolfgang Denk
[not found] ` <410123EE.4000602@intracom.gr>
2004-07-23 15:56 ` Mark Chambers [this message]
2004-07-23 17:22 ` Wolfgang Denk
2004-07-23 21:06 ` Linux is not reliable enough? Kevin P. Dankwardt
2004-07-24 3:02 ` Linh Dang
2004-07-24 6:29 ` Der Herr Hofrat
2004-07-25 16:23 ` Wolfgang Denk
2004-07-24 11:35 ` Mark Chambers
2004-07-24 22:14 ` MPC8245 Error No. 26 DeLaGarza, Robert
2004-07-26 7:49 ` Linux is not reliable enough? Marius Groeger
2004-07-26 13:46 ` Mark Chambers
2004-07-26 14:31 ` Der Herr Hofrat
2004-07-26 15:42 ` Marius Groeger
2004-07-27 11:20 ` Robert Kaiser
2004-07-27 13:29 ` Mark Chambers
2004-07-24 21:44 ` Sylvain Munaut
2004-07-25 3:00 ` Could 2_4_devel support RPXlite DW LCD panel? Song Sam
-- strict thread matches above, loose matches on Subject: below --
2004-07-22 17:10 random ramblings on 8xx patches (long and tedious :-) Wells, Charles
2004-07-22 17:35 ` Dan Malek
2004-07-23 8:48 ` Jaap-Jan Boor
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='00a601c470cd$94f5cd80$0301a8c0@chuck2' \
--to=markc@mail.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=panto@intracom.gr \
--cc=rpjday@mindspring.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).