embedded PowerPC porting coordination [was Re: Motorola Web Site]

embedded PowerPC porting coordination [was Re: Motorola Web Site]

[Charles Lepple]

Wolfgang Denk wrote:
> To support a  broader  range  ofborads  some  cleanup  is  necessary,
> isolating  HW  dependent  parts  of  the  code  in "BSP" like groups,
> allowing for easier configuration of device configuration,  port  pin
> assignment etc.

I'm not exactly volunteering for the job of coordinating this, but I
would have to agree. Would it make sense to start another list
("linuxppc-embedded," perhaps?) to discuss this at greater length?

--Charles Lepple
clepple@mitre.org


[[ This message was sent via the linuxppc-dev mailing list.  Replies are ]]
[[ not  forced  back  to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting.   ]]

Re: embedded PowerPC porting coordination [was Re: Motorola Web Site]

[Adrian Cox]

Charles Lepple wrote:
> Wolfgang Denk wrote:
> > To support a  broader  range  ofborads  some  cleanup  is  necessary,
> > isolating  HW  dependent  parts  of  the  code  in "BSP" like groups,
> > allowing for easier configuration of device configuration,  port  pin
> > assignment etc.
> 
> I'm not exactly volunteering for the job of coordinating this, but I
> would have to agree. Would it make sense to start another list
> ("linuxppc-embedded," perhaps?) to discuss this at greater length?

Another thing to consider - linuxppc-dev is already a mix of PPC kernel
development, and linuxppc distribution userspace issues. I've ported
2.2.10 to my embedded board, but I'm using a Debian userspace.

The PPC kernel is halfway towards a sensible BSP structure already - all
it needs is some tidying up, a sensible directory structure for BSPs,
and a few new conditions like CONFIG_PPC_HAVE_OPEN_FIRMWARE. The main
area to work on is arch/ppc/mm/init.c, which has to have too many board
specific functions in its current form.

- Adrian Cox, AG Electronics.

[[ This message was sent via the linuxppc-dev mailing list.  Replies are ]]
[[ not  forced  back  to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting.   ]]

Re: embedded PowerPC porting coordination [was Re: Motorola Web Site]

[Hartmut Koptein]

> Another thing to consider - linuxppc-dev is already a mix of PPC kernel
> development, and linuxppc distribution userspace issues. I've ported
> 2.2.10 to my embedded board, but I'm using a Debian userspace.

Please forward me your patches. 

Thanks,

  Hartmut

[[ This message was sent via the linuxppc-dev mailing list.  Replies are ]]
[[ not  forced  back  to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting.   ]]

Re: embedded PowerPC porting coordination [was Re: Motorola Web Site]

[Wolfgang Denk]

In message <19990731124856.F18628@isis.isis.de> you write:
> 
[Adrian Cox:]
> > Another thing to consider - linuxppc-dev is already a mix of PPC kernel
> > development, and linuxppc distribution userspace issues. I've ported
> > 2.2.10 to my embedded board, but I'm using a Debian userspace.
> 
> Please forward me your patches. 

Me too :-)

Wolfgang Denk

-- 
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd@denx.de
I have a theory that it's impossible to prove anything, but  I  can't
prove it.

[[ This message was sent via the linuxppc-dev mailing list.  Replies are ]]
[[ not  forced  back  to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting.   ]]