public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Patch: Support for PQ27e (8247/48/71/72) chips and MPC8272ADS board
Date: Tue, 23 Mar 2004 22:38:04 +0100	[thread overview]
Message-ID: <20040323213809.2FAB4C0655@atlas.denx.de> (raw)
In-Reply-To: Your message of "Tue, 16 Mar 2004 08:37:33 CST." <761C62B8-7757-11D8-A4C6-000393DBC2E8@motorola.com>

In message <761C62B8-7757-11D8-A4C6-000393DBC2E8@motorola.com> you wrote:
> 
> I agree with only enabling ports that will be used.  I guess I would  
> expect the port to be used in Linux.  I'm working on an updated 2.6 SCC  
> uart driver and realized that I needed to enable the 2nd port in BCSR.   
> I had expected that u-boot would have already handled it.

The philosophy is to enable  and/or  initialize  only  those  devices
which are actually used by U-Boot itself. Even the network interfaces
get  initialized  only at the moment when you issue the first command
to access the network.

On the other hand a Linux device driver should assume  it  finds  the
device  in  an  unknown  random  (*)  state,  it  should  perform all
initialization it needs itself, and it should deinitialize the device
(if the driver should get unloaded) into an idle state.

(*) "random" is not completely random, of course - it  still  assumes
that  the device is well-behaving, i. e. that interrupts are disabled
etc.

Best regards,

Wolfgang Denk

-- 
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd at denx.de
"When anyone says `theoretically,' they really mean `not really.'"
- David Parnas

      parent reply	other threads:[~2004-03-23 21:38 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-29 19:04 [U-Boot-Users] Patch: Support for PQ27e (8247/48/71/72) chips and MPC8272ADS board Yuli Barcohen
2004-03-13 23:54 ` Wolfgang Denk
2004-03-15  9:45   ` [U-Boot-Users] " Yuli Barcohen
2004-03-15 10:07     ` Wolfgang Denk
2004-03-15 13:25       ` Yuli Barcohen
2004-03-15 13:37         ` Wolfgang Denk
2004-03-17 11:46           ` Yuli Barcohen
2004-03-17 14:15             ` Dan Malek
2004-03-17 15:12               ` Yuli Barcohen
2004-03-17 21:18                 ` Wolfgang Denk
2004-03-18  8:54                   ` Yuli Barcohen
2004-03-17 17:21             ` Kumar Gala
2004-03-17 17:39               ` Yuli Barcohen
2004-03-16  6:51 ` [U-Boot-Users] " Kumar Gala
2004-03-16  7:23   ` Yuli Barcohen
2004-03-16 14:37     ` Kumar Gala
2004-03-17 10:54       ` Yuli Barcohen
2004-03-17 15:03         ` Kumar Gala
2004-03-23 21:38       ` Wolfgang Denk [this message]

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=20040323213809.2FAB4C0655@atlas.denx.de \
    --to=wd@denx.de \
    --cc=u-boot@lists.denx.de \
    /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