Re: calling firmware code data is not being honest with ourselves, includes counterproposal and RFC on a possible Amendment
On Wed, Aug 30, 2006 at 10:00:43PM -0400, David Nusinow wrote:
> On Wed, Aug 30, 2006 at 09:54:31PM -0400, David Nusinow wrote:
> > On Wed, Aug 30, 2006 at 10:41:00PM -0700, Thomas Bushnell BSG wrote:
> > > David Nusinow <firstname.lastname@example.org> writes:
> > >
> > > > Would you, or someone else, mind pointing out some examples of firmware
> > > > with source? Preferrably with some of the breadth you refer to above? I
> > > > understand firmware in concept, but beyond seeing it as a binary blob I've
> > > > not really come seriously in to contact with it. If I'm going to vote on
> > > > this issue, I'd really like to actually understand what I'm going to be
> > > > voting on.
> > >
> > > I think it's widely in agreement that hardware manufacturers have
> > > assemblers and other tools they use for building firmware.
> > So we don't have any firmware with source?
> Sorry. I've since read further in to this thread and found answers. I'll
> grab the kernel code and have a look.
The kernel source has firmware with source for the keyspan PDA USB
serial dongle (linux-184.108.40.206/drivers/usb/serial/keyspan_pda.S).
has firmware with source for some M-audio midisport midi interfaces.
sdcc is needed for compilation.
L & L
Goa is a state of mind