linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Hollis Blanchard <hollis@penguinppc.org>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org, linux-usb-devel@lists.sourceforge.net
Subject: Re: [PATCH] Add USB to MPC8349 PB platform support
Date: Mon, 17 Jul 2006 16:08:14 -0400	[thread overview]
Message-ID: <1153166894.4459.4.camel@basalt.austin.ibm.com> (raw)
In-Reply-To: <A4F686A1-9558-4DD0-BF4C-BB64494BB719@kernel.crashing.org>

On Mon, 2006-07-17 at 14:16 -0500, Kumar Gala wrote:
> On Jul 14, 2006, at 11:21 AM, Li Yang wrote:
> 
> > On 7/14/06, Kumar Gala <galak@kernel.crashing.org> wrote:
> >> Nack, my expectation is this is all setup by the boot loader.
> >
> > That's a good wish. ;)  However, USB is not required by bootloader. So
> > it is not likely to be initialized there.  And if we put it in
> > bootloader, it will be hard to change the mode(MPH/DR), which requires
> > a re-burn of bootloader.  It's better that we make sure it's correctly
> > configured here.
> 
> I disagree.  You are coming from this from a board that does  
> everything under the sun.  I'd like to avoid having this type of  
> initialization in the kernel.  There is a whole additional kitchen  
> sink that could move into the kernel as well.

Seems to me that it's far better to have init code in the kernel than
firmware. For one example, look at the x86 video card init problem
PowerPC Linux has. It's also far easier to fix/deploy Linux code than
firmware code, as Li observed, and on top of that it's less work for
non-UBoot firmwares in the future.

-Hollis

  reply	other threads:[~2006-07-17 20:08 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-14 11:52 [PATCH] Add USB to MPC8349 PB platform support Li Yang
2006-07-14 13:49 ` Kumar Gala
2006-07-14 16:21   ` Li Yang
2006-07-17 19:16     ` Kumar Gala
2006-07-17 20:08       ` Hollis Blanchard [this message]
2006-07-17 22:57         ` [linux-usb-devel] " David Brownell
2006-07-18  6:34           ` Li Yang-r58472
2006-07-19 20:13         ` Timur Tabi
2006-07-19 20:48           ` Kumar Gala
2006-07-17 20:17       ` Dan Malek
2006-07-17 21:39         ` Kumar Gala
2006-07-17 22:12           ` Dan Malek
2006-07-18  7:40           ` Li Yang-r58472
2006-07-18 13:52             ` Kumar Gala
2006-07-18 15:19               ` Dan Malek
2006-07-18 15:53               ` Wolfgang Denk
2006-07-19  6:30               ` Li Yang-r58472
2006-07-19 13:14                 ` Kumar Gala
2006-07-19 15:42                   ` Dan Malek
2006-07-19 18:59                     ` Li Yang
2006-07-19 19:19                       ` [linux-usb-devel] " Pete Zaitcev
2006-07-20  6:45                         ` Li Yang-r58472
2006-08-01 15:36                       ` David Brownell
2006-07-19 20:19                     ` Marc Leeman
2006-07-19 20:55                       ` Kumar Gala
2006-07-20  7:21                         ` Marc Leeman
2006-07-20 13:19                           ` Kumar Gala
2006-07-19 20:09 ` Kumar Gala
2006-07-20  6:32   ` Li Yang-r58472

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=1153166894.4459.4.camel@basalt.austin.ibm.com \
    --to=hollis@penguinppc.org \
    --cc=galak@kernel.crashing.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    --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).