From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from fed1rmmtao09.cox.net (fed1rmmtao09.cox.net [68.230.241.30]) by ozlabs.org (Postfix) with ESMTP id AA8632BDEB for ; Thu, 11 Nov 2004 07:38:02 +1100 (EST) Date: Wed, 10 Nov 2004 11:39:09 -0700 From: Matt Porter To: Rick McBain Message-ID: <20041110113909.A22167@home.com> References: <20041110081516.B20590@home.com> <000801c4c746$d271d490$6602a8c0@RicksPresario900> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <000801c4c746$d271d490$6602a8c0@RicksPresario900>; from rick.mcbain@logicsense.com on Wed, Nov 10, 2004 at 09:00:40AM -0800 Cc: linuxppc-embedded@ozlabs.org Subject: Re: Linux port for the 440EP processor List-Id: Linux on Embedded PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Wed, Nov 10, 2004 at 09:00:40AM -0800, Rick McBain wrote: > Been there, done that. The only code they will hand out is the custom > IBM OS stuff they have. I have talked to the VP of the embedded > processor division, all the way on down. Bummer. > But I would be happy if somebody would prove me wrong - I think the semi > makers should provide Linux drivers available on their website. I know > AMD has a bunch of drivers for their embedded chips on theirs. Actually, I'd rather see the code in the mainline tree where it can be maintained. Stuff on vendor sites tends to mold. > Any Linux code, at this point anyways, has to be gotten from somebody > other than AMCC. However, I will be speaking to their director of > software engineering tommorrow, about all these Linux issues. Maybe > things will change. Sounds good. -Matt