Re: [PATCH] Input: elants_i2c - zero-extend hardware ID in firmware name

On Fri, Apr 17, 2015 at 8:43 PM, Dmitry Torokhov wrote: > Let's zero-extend hardware id number when forming firmware file name, > to avoid kernel requesting firmware like "elants_i2c_ 0.bin", which > is quite unexpected. > > Signed-off-by: Dmitry Torokhov > --- > drivers/input/touchscreen/elan

Re: [PATCH] firmware_class: Add firmware filename overrides

Okay, thanks for the reviews. My hope was to avoid having to add that feature into each driver, but that's okay. -Charlie On Fri, Mar 6, 2015 at 3:33 PM, Marcel Holtmann wrote: > Hi Charles, > Specifically this was motivated by a situation where we have one device with

Re: [PATCH] firmware_class: Add firmware filename overrides

On Thu, Mar 5, 2015 at 5:27 PM, Ming Lei wrote: > On Fri, Mar 6, 2015 at 6:36 AM, Dmitry Torokhov wrote: >> On Thu, Mar 5, 2015 at 2:12 PM, Marcel Holtmann wrote: >>> Hi Dmitry, >>> >> Specifically this was motivated by a situation where we have one >> device with a dual-sourced

Re: [PATCH] firmware_class: Add firmware filename overrides

On Thu, Mar 5, 2015 at 9:39 AM, Marcel Holtmann wrote: > Hi Charles, > >> Specifically this was motivated by a situation where we have one >> device with a dual-sourced touchscreen. Both use the same driver but >> have different hardware & fw. Our FW updating software therefore, >> needs to be abl

Re: [PATCH] firmware_class: Add firmware filename overrides

Specifically this was motivated by a situation where we have one device with a dual-sourced touchscreen. Both use the same driver but have different hardware & fw. Our FW updating software therefore, needs to be able to update with the correct FW and detect all this at runtime due to a read-only pa