From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp114.sbc.mail.mud.yahoo.com (smtp114.sbc.mail.mud.yahoo.com [68.142.198.213]) by ozlabs.org (Postfix) with SMTP id 5515867BAD for ; Tue, 18 Jul 2006 09:04:34 +1000 (EST) From: David Brownell To: linux-usb-devel@lists.sourceforge.net Subject: Re: [linux-usb-devel] [PATCH] Add USB to MPC8349 PB platform support Date: Mon, 17 Jul 2006 15:57:49 -0700 References: <44B7857A.2060101@freescale.com> <1153166894.4459.4.camel@basalt.austin.ibm.com> In-Reply-To: <1153166894.4459.4.camel@basalt.austin.ibm.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Message-Id: <200607171557.50368.david-b@pacbell.net> Cc: linuxppc-dev@ozlabs.org List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Monday 17 July 2006 1:08 pm, Hollis Blanchard wrote: > > Seems to me that it's far better to have init code in the kernel than > firmware. If there's a general Linux policy on the issue, I think that'd be it. Plus, remember that boot firmware _can't_ always be changed/bugfixed; sometimes it can, but not as a general rule. - Dave > 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 >