Menu
▾
▴
Re: [Acx100-devel] TNETW1100B driver for IPAQ 6300
|
From: Bas V. <bve...@bl...> - 2005-10-28 22:05:02
|
I'm starting to do the same, and was wondering whether Husam made any further progress. I've added a mem.c, implementing the PCI functions, and am missing the information where the memory regions start and stop. I'm also not clear on whether it uses DMA or not, but I'm trying to find out. Some questions I have now: How do I recognize both memory regions? I know the PCI devices have two memory regions, and would like to make sure I've got the same (if necessary). Let me know, and perhaps we can help each other out. On Tue, 2005-09-20 at 10:55 +0100, Husam Senussi wrote: > Yes I had change the code because this not PCI card, it's connected > using 16 bit Slave interface, the code is base on MailScanner has > detected a possible fraud attempt from "195.66.192.167" claiming to > beacx-20050917.tar.bz2MailScanner has detected a possible fraud > attempt from "195.66.192.167" claiming to be . > > Last night I replaced the memcpy for mailbox with functions uses > IO_ACX_SLV_* registers to copy command parameters and I manage to get > it working only when I read or write using > acx_read_reg32/acx_write_reg32. "So far I'm not getting invalid > element information" > > For some reason the 16 bit failling!!! > > IPAQ processer is lettel endian it's OMAP1510 processer based on > ARM925T chip. > > I'm attaching the firmware that comes with the device > > BTW is there any easyI can conform that the output from issue command > is correct!!! > > Thanks > Husam > > > On 9/20/05, Denis Vlasenko <vd...@il...> wrote: > On Monday 19 September 2005 21:21, hus...@gm... > wrote: > > Hi Denis, > > > > I have used the firmware that comes with wince driver and > thats the only > > one !!! > > could be problem with Command Mailbox offset, I tried to use > IO_ACX_SLV_ > > registers to copy the data instead of just memcpy but I > keept getting "IRQ > > polling timed out" . > > > > Anyway I'm attaching my log files > > > > Thanks > > > > >From: Denis Vlasenko <vd...@il...> > > >To: acx...@li... > > >Subject: Re: [Acx100-devel] TNETW1100B driver for IPAQ 6300 > > >Date: Mon, 19 Sep 2005 08:25:41 +0300 > [large useless quoting snipped] > > > > Jan 1 03:34:00 h6300 user.warn kernel: cmd_type 0x0000, > cmd_status 0x0000 > > > > [Idle] > > > > Jan 1 03:34:00 h6300 user.warn kernel: 01253018 > ==> acx_s_msleep > > > > Jan 1 03:34:00 h6300 user.warn kernel: 01253025 > <== acx_s_msleep > > > > Jan 1 03:34:00 h6300 user.warn kernel: cmd_type 0x0001, > cmd_status 0x0003 > > > > [Invalid Information Element] > > > > Jan 1 03:34:00 h6300 user.warn kernel: wlan%d: > issue_cmd(): cmd_status is > > > > not SUCCESS: 3 (Invalid Information Element). To > > > > Jan 1 03:34:00 h6300 user.warn kernel: wlan%d: > > > > issue_cmd(cmd:ACX1xx_CMD_INTERROGATE) FAILED > > > > > >I suspect you loaded wrong primary firmware. > > > > > >Send the whole log, not linewrapped. > > From the log: > Compact Flash module v0.3.10 initialized, waiting for cards to > probe... > > Obviously you made some changes. There is no such message in > 0.3.10 driver. > Can you show your changes in diff -urpn form? > > Jan 1 03:33:56 h6300 user.warn kernel: requesting firmware > image 'tiacx100c0D' > Jan 1 03:33:56 h6300 user.warn kernel: acx: firmware image > 'tiacx100c0D' was not provided. Check your hotplug scripts > Jan 1 03:33:56 h6300 user.warn kernel: requesting firmware > image 'tiacx100' > Jan 1 03:33:56 h6300 user.warn kernel: not using auto > increment for firmware loading > ... > Jan 1 03:34:00 h6300 user.warn kernel: 01253015 ==> > acx_s_upload_radio > Jan 1 03:34:00 h6300 user.warn kernel: interrogate > (type:ACX1xx_IE_MEMORY_MAP,len:40) > Jan 1 03:34:00 h6300 user.warn kernel: 01253016 ==> > acxpci_s_issue_cmd_timeo_debug > Jan 1 03:34:00 h6300 user.warn kernel: issue_cmd > (cmd:ACX1xx_CMD_INTERROGATE,buflen:44,timeout:50ms,type:0x0008) > Jan 1 03:34:00 h6300 user.warn kernel: cmd_type 0x0000, > cmd_status 0x0000 [Idle] > Jan 1 03:34:00 h6300 user.warn kernel: 01253018 ==> > acx_s_msleep > Jan 1 03:34:00 h6300 user.warn kernel: 01253025 <== > acx_s_msleep > Jan 1 03:34:00 h6300 user.warn kernel: cmd_type 0x0001, > cmd_status 0x0003 [Invalid Information Element] > Jan 1 03:34:00 h6300 user.warn kernel: wlan%d: issue_cmd(): > cmd_status is not SUCCESS: 3 (Invalid Information Element). > Took 10ms of 49 > Jan 1 03:34:00 h6300 user.warn kernel: wlan%d: issue_cmd > (cmd:ACX1xx_CMD_INTERROGATE) FAILED > Jan 1 03:34:00 h6300 user.warn kernel: [<c0023a88>] > (dump_stack+0x0/0x14) from [<bf01c5a8>] > (acxpci_s_issue_cmd_timeo_debug+0x440/0x4d4 [acx]) > Jan 1 03:34:00 h6300 user.warn kernel: [<bf01c168>] > (acxpci_s_issue_cmd_timeo_debug+0x0/0x4d4 [acx]) from > [<bf0139fc>] (acx_s_interrogate_debug+0x7c/0xb4 [acx]) > Jan 1 03:34:00 h6300 user.warn kernel: [<bf013980>] > (acx_s_interrogate_debug+0x0/0xb4 [acx]) from [<bf01c698>] > (acx_s_upload_radio+0x5c/0x240 [acx]) > Jan 1 03:34:00 h6300 user.warn kernel: r8 = 00000000 r7 = > 00000000 r6 = 00000001 r5 = C3504220 > Jan 1 03:34:00 h6300 user.warn kernel: r4 = C3504220 > > This is not good. Still looks like you are loading wrong > file. > fw which is proven working can be found here: > > MailScanner warning: numerical links are often > malicious:http://195.66.192.167/linux/acx_patches/fw/acx100_1.9.8.b/ > > Also please send me your fw file(s). > > BTW, which processor is in these ipaqs? Is it big-endian? > -- > vda > -- Bas Vermeulen <bve...@bl...> |