circa 1/24/03 14:56, Bill Rector <email@hidden> wrote:
> I've pretty much decided that what I'm doing requires a kernel driver. My
> driver needs to handle the following services:
> 1. Firmware loader. My hardware uses a I2C 32KB EEProm for boot and
> configurations and a 512KB Flash for MPU code and programmable logic
> firmware storage. By using the Cypress MPU, I can program a brand new or
> previous unit with new firmware. This also means that for new or wiped
> units, the service or client will need to also look for the default Cypress
> 0547 vendor ID. I suppose this can be done as personality setting in the
> kext's plist.
This part definitely doesn't need to be in the kernel. You could write a
startup item instead. A startup item is just a regular userland process. I
have a firmware loader startup item process which handles Cypress chips and
DFU. It works very well. You could also have a separate GUI app which only
runs by explicit request of the user, but for my case this didn't make sense
because some of the devices I support always need firmware (software,
actually) when they are plugged in.
> 2... 3...
I'll leave these to someone else.
--
Pete Gontier -- pete at m-audio dot com -- <http://www.m-audio.com/>
_______________________________________________
usb mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/usb
Do not post admin requests to the list. They will be ignored.
