Hi,
yesterday I started to write an MI driver for the Catweasel MK3 and MK4 PCI
boards (http://www.icomp.de/indexe.htm).
The card is recognized, the io space is mapped and the hardware is
initialized (firmware uploaded into the card's FPGA).
ATM I have two questions:
1. The firmware is large, w
On Sat, Feb 06, 2010 at 01:33:33PM +0100, Frank Wille wrote:
> 1. The firmware is large, with about 60k. Does anybody have experience
> with using a compressed firmware image in the driver, which is uncompressed
> on the fly, while uploading it to the chip? How would I do that?
> (This would probab
I think it's called firmload(9).
Masao
Joerg Sonnenberger wrote:
> Can't you use the approach e.g. of the wpi(4) driver and load the
> firmware image from the filesystem?
No, firmload(9) would not really be an option, because I want to detect
connected devices, like a keyboard and floppy disk drives during boot.
Without the firmware t
Probably we can think of a nice way to apply modules(9) to load a firmware
image, upload it to the device, then unload. When firmload(9) was invented,
we didn't have a nice kernel module support yet.
(I'm not sure what the dependency of them will look like, tho. :)
Masao
Masao Uebayashi wrote:
> Probably we can think of a nice way to apply modules(9) to load a
> firmware image, upload it to the device, then unload. When firmload(9)
> was invented, we didn't have a nice kernel module support yet.
As I understand this would also need a filesystem to load from?
B
On 6 February 2010 13:33, Frank Wille wrote:
> Joerg Sonnenberger wrote:
>
>> Can't you use the approach e.g. of the wpi(4) driver and load the
>> firmware image from the filesystem?
>
> No, firmload(9) would not really be an option, because I want to detect
> connected devices, like a keyboard an
On Sat, 6 Feb 2010 18:46:56 +
David Brownlee wrote:
> firmload can currently load from a set of directories. Has anyone
> considered extending firmload to optionally load from memory as well -
> possibly an included ramdisk image? That would allow the choice of
> building in firmware images w
1. The firmware is large, with about 60k. Does anybody have experience
with using a compressed firmware image in the driver, which is uncompressed
on the fly, while uploading it to the chip? How would I do that?
(This would probably make sense for most firmware, so a common interfac
> > Probably we can think of a nice way to apply modules(9) to load a
> > firmware image, upload it to the device, then unload. When firmload(9)
> > was invented, we didn't have a nice kernel module support yet.
>
> As I understand this would also need a filesystem to load from?
Can be loaded by
10 matches
Mail list logo
