From: Nathael PAJANI <nathael.pajani@cpe•fr>
To: linuxppc-embedded@ozlabs•org
Subject: Re: MPC8555 8280/8270 USB host support
Date: Thu, 01 Dec 2005 16:41:03 +0100 [thread overview]
Message-ID: <438F198F.9020606@cpe.fr> (raw)
Hi
>
>>
>>Don't you think u-boot should take care of clock setup
>>i.e. as much as possible of all board dependent stuff ?
>>
>>
>I think you're right, but then it was easier to make all these setups
>in the driver itself.
>
If u-boot is the boot loader of your board (the stuff running on it
--before-- we see this:
loaded at: 00400000 005153B4
board data at: 00513130 00513334
relocated to: 00405090 00405294
zimage at: 00405A85 00512099
avail ram: 00516000 08000000
Linux/PPC load: rw console=ttyS0 root=/dev/nfs ip=on
Uncompressing Linux...done)
Then I would say NO
If u-boot is this exact stuff (the files in arch/ppc/boot/simple/...
misc-embedded.c for example)
then, yes, this is somehow better.
But (tell me if I'm wrong) this is not really Linux code, and this
should be done by Linux.
What I think should be good also is the platform files
(arch/ppc/platforms/....) for this is the place where all the board
dependant stuff stays.
Maybe I'm completely mistaken.
Feel free to tell me (and explain please !)
Have fun.
next reply other threads:[~2005-12-01 15:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-01 15:41 Nathael PAJANI [this message]
2005-12-01 17:37 ` MPC8555 8280/8270 USB host support Wolfgang Denk
-- strict thread matches above, loose matches on Subject: below --
2005-10-07 5:05 Problem Regarding Ping in Linux kernel version 2.4.24 apoorv sangal
2005-10-12 6:59 ` MPC8555 USB host support Stefan Roese
2005-10-12 7:11 ` Mike Rapoport
2005-10-12 7:27 ` Stefan Roese
2005-10-12 12:34 ` Alex Zeffertt
2005-10-31 6:45 ` Mike Rapoport
[not found] ` <1131960060.7748.9.camel@hawk.pwav.net>
2005-11-15 6:59 ` Mike Rapoport
2005-12-01 12:26 ` MPC8555 8280/8270 " Hans Schillstrom
2005-12-01 13:55 ` Mike Rapoport
2005-12-01 15:29 ` Wolfgang Denk
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=438F198F.9020606@cpe.fr \
--to=nathael.pajani@cpe$(echo .)fr \
--cc=linuxppc-embedded@ozlabs$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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