Hello, On Thu, Jan 8, 2009 at 11:57 PM, Florian Fainelli <flor...@openwrt.org> wrote: > Le Thursday 08 January 2009 23:47:58 Leon Woestenberg, vous avez écrit :
>> The programming back end should be generic enough so that it can use >> other subsystems. >> > That's the idea behind using request_firmware, which provides you with both a > pointer to the data and the size of the blob. I know, that's what I would call the front-end (near userspace). I meant the low-level back-end (towards hardware): > - fpgaload-core which contains all the code that can be shared > between the drivers like requesting firmware, providing sysfs > attributes, > - fpgaload-spi would handle the low-level SPI connection > - fpgaload-par would handle the low-level parallel connection > > fpgaload-ser and par would register with fpgaload-core and they could > register a fpga loading callback which is low-level specific for > instance. My $0.02 was: Those callbacks should also be able to accept chunks of data (preferably in the same way using ptr/len). Regards, -- Leon -- To unsubscribe from this list: send the line "unsubscribe linux-embedded" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html