Then, is it time to establish a common
reference implementation?
For the record, this project tends to
build system-on-chip processor with graphic
device controllers integrated to make
printer controller boards with one single chip..
And we have chosen an ARM926 IP design
(from ARM) and debian 2.6.4 as rtos
to support printer firmware
Bye
Olivier
lsorense@csclub.uwaterloo.ca
(Lennart Sorensen)
19/10/2004 15:19
To
olivier.delouya@takasic.fr
cc
debian-arm@lists.debian.org
Subject
Re: ARM-Linux guide lines
On Tue, Oct 19, 2004 at 10:25:29AM +0200, olivier.delouya@takasic.fr
wrote:
> I am currently building a development platform for embedded arm-linux
> firmware
> I write some generation / install scripts, I tune the kernel, trick
some
> bootstrap sequences
> to tailor to my own need, I add features to the ramdisk, as needed,
that I
> download on package form
> from various sources..
> The goal is to provide an open source rtos + dev tools alternative,
free
> of charge and license (except GPL!)
> to the printer manufacturer industry
>
> All this is some how "hand made" !
>
> Is there some kind of methodology, guidelines to generate a consistent
> development platform on ARM/Linux?
> Is there a common source?
>
> I can share my own accomplishment if some one is interested
At this point I get the impression that there aren't even two arm boards
out there with compatible boot systems. Arm systems are all over
the
place in terms of hardware used to clue the cpu to other bits of
hardware, and each seems to have its own firmware and boot procedure.
This is not like systems where open firmware exists for reference
systems that everyone (mostly) agree to use where writing a boot laoder
and hardware detection code for the kernel is fairly easy.