Thanks Joe, I've set that ctp_firmware parameter with relative and complete path, but the kernel doesn't seem to be able to find it. I was told to use /lib/firmware, and it fails with the same error, and the kernel I'm using (3.4.79+), hasn't a very detailed debugging of where it is searching. Is there a more bullet proof good way to load the firmware?, or, how can I debug where the kernel is trying to load the firmware from?
Many thanks in advance! El viernes, 23 de mayo de 2014 05:03:02 UTC-3, Joe Burmeister escribió: > > Hi, > > The driver gets the file location from the fex file, from "ctp_firmware". > There is no point having a standard location because the firmware device > can not be generic. There needs to be a different one for every hardware > configuration. > > Joe > > > > On 23/05/14 03:46, [email protected] <javascript:> wrote: > > I have compiled the gslx680 driver, but there is a problem finding the > firmware file (Error -2). Is there an standard location where the module > will search for it? > I'm using a 3.4 kernel, and the F20 image. Many thanks! > > Module loading dmesg excerpt following: > > [ 342.700742] > ===========================gslx680_ts_init===================== > [ 342.704643] _fetch_sysconfig_para. > [ 342.708780] gslx680 firmware /lib/firmware/tablet.fw. > [ 342.718037] _fetch_sysconfig_para: after: ctp_twi_addr is 0x40, > dirty_addr_buf: 0x40. dirty_addr_buf[1]: 0xfffe > [ 342.722046] _fetch_sysconfig_para: ctp_twi_id is 2. > [ 342.726244] _fetch_sysconfig_para: screen_max_x = 800. > [ 342.730476] _fetch_sysconfig_para: screen_max_y = 480. > [ 342.734587] _fetch_sysconfig_para: revert_x_flag = 1. > [ 342.738699] _fetch_sysconfig_para: revert_y_flag = 1. > [ 342.743223] _fetch_sysconfig_para: exchange_x_y_flag = 1. > [ 342.748665] _init_platform_resource: tp_io request gpio fail! > [ 342.760743] i2c-core: driver [gslx680] using legacy suspend method > [ 342.772884] i2c-core: driver [gslx680] using legacy resume method > [ 342.781601] incomplete xfer (0x20) > [ 342.786900] incomplete xfer (0x20) > [ 342.793411] ctp_detect: Detected chip gslx680 at adapter 2, address 0x40 > [ 342.797667] ====gslx680_ts_probe begin=====. > [ 342.801305] ==kzalloc success= > [ 342.804136] [GSLX680] Enter gsl_ts_init_ts > [ 342.808394] ctp_set_irq_mode: config gpio to int mode. > [ 342.815161] ctp_set_irq_mode, 854: gpio_int_info, port = 8, port_num = > 21. > [ 342.817574] INTERRUPT CONFIG > [ 342.825989] input: gslx680 as > /devices/platform/sunxi-i2c.2/i2c-2/2-0040/input/input1 > [ 342.920231] =============gsl_load_fw start============== > [ 404.034587] gslx680 2-0040: Unable to open firmware > /lib/firmware/tablet.fw > [ 404.045146] init_chip: gsl_load_fw fail: -2 > [ 404.048717] gslx680 2-0040: init_chip failed > [ 404.057737] gslx680: probe of 2-0040 failed with error -2 > -- > You received this message because you are subscribed to a topic in the > Google Groups "linux-sunxi" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/linux-sunxi/SZGxiTQcFyY/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected] <javascript:>. > For more options, visit https://groups.google.com/d/optout. > > > -- You received this message because you are subscribed to the Google Groups "linux-sunxi" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
