[<prev] [next>] [day] [month] [year] [list]
Message-ID: <4879B0C6C249214CBE7AB04453F84E4D0509A9@zch01exm20.fsl.freescale.net>
Date: Tue, 18 Jul 2006 14:34:29 +0800
From: "Li Yang-r58472" <LeoLi@...escale.com>
To: "David Brownell" <david-b@...bell.net>,
<linux-usb-devel@...ts.sourceforge.net>,
<linux-kernel@...r.kernel.org>
Cc: "Hollis Blanchard" <hollis@...guinppc.org>,
"Kumar Gala" <galak@...nel.crashing.org>, <linuxppc-dev@...abs.org>
Subject: RE: [linux-usb-devel] [PATCH] Add USB to MPC8349 PB platform support
> -----Original Message-----
> From: David Brownell [mailto:david-b@...bell.net]
> Sent: Tuesday, July 18, 2006 6:58 AM
> To: linux-usb-devel@...ts.sourceforge.net
> Cc: Hollis Blanchard; Kumar Gala; linuxppc-dev@...abs.org; Li
Yang-r58472
> Subject: Re: [linux-usb-devel] [PATCH] Add USB to MPC8349 PB platform
support
>
> 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.
Do we have a general policy for this now?
>
> 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
> >
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists