LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
* Re: UWB, WUSB, and WLP subsystems for 2.6.28
       [not found] ` <6f3df9eb-5c1a-4ee1-a78f-7c0ff55a42fc@t18g2000prt.googlegroups.com>
@ 2008-10-23  9:00   ` David Vrabel
  2008-10-24  2:13     ` Law Sie Yong
                       ` (3 more replies)
  0 siblings, 4 replies; 5+ messages in thread
From: David Vrabel @ 2008-10-23  9:00 UTC (permalink / raw)
  To: sylaw; +Cc: Kernel development list

sylaw@i2r.a-star.edu.sg wrote:
> 
>   I am currently working on trying to WUSB linux to work on DLINK
> dub1210 dongle. Does the 2.6.26-rc8 of WUSB UWB linux work with
> DUB1210, as when i try to connect to the DLINK UWB Hub it show me
> error when it try to enumerate the hub i believe. Your help is greatly
> appreciated ! thx in advance !

The WUSB hub (DWA) won't do anything useful because there's no DWA
driver.  However, you should be able to authenticate and enumerate it.

Could you expand on the error messages?  It may be useful to build the
driver with additional debugging.

David
-- 
David Vrabel, Senior Software Engineer, Drivers
CSR, Churchill House, Cambridge Business Park,  Tel: +44 (0)1223 692562
Cowley Road, Cambridge, CB4 0WZ                 http://www.csr.com/

^ permalink raw reply	[flat|nested] 5+ messages in thread

* RE: UWB, WUSB, and WLP subsystems for 2.6.28
  2008-10-23  9:00   ` UWB, WUSB, and WLP subsystems for 2.6.28 David Vrabel
@ 2008-10-24  2:13     ` Law Sie Yong
  2008-10-29  1:27     ` Law Sie Yong
                       ` (2 subsequent siblings)
  3 siblings, 0 replies; 5+ messages in thread
From: Law Sie Yong @ 2008-10-24  2:13 UTC (permalink / raw)
  To: David Vrabel; +Cc: Kernel development list

Hi David,

Thx for the prompt reply. I will attach the error message soon. BTW, is IOGear Wireless usb dongle (i believe its using Intel i1480 MAC) with RC1.3 firmware confirm to work with the IOGear UWB HUB and be able to detect the mass storage device attached to the hub? or the open source also doesnt have the DWA driver for IOGear HUB?  In addition, i tried to download the UWB for kernel 2.6.28 from git://git.kernel.org/pub/scm/linux/kernel/git/dvrabel/uwb.git for-upstream, but it doesnt contain any UWB code. i use the "git clone http://www.kernel.org/pub/scm/linux/kernel/git/dvrabel/uwb.git for-upstream" command to download as i cant use "git clone git://git.kernel.org/pub/scm/linux/kernel/git/dvrabel/uwb.git for-upstream", error say cant connect.  thx again !







thx again !



Law Sie Yong
Senior Research Officer
Communication Systems Department



-----Original Message-----
From: David Vrabel [mailto:david.vrabel@csr.com]
Sent: Thu 10/23/2008 5:00 PM
To: Law Sie Yong
Cc: Kernel development list
Subject: Re: UWB, WUSB, and WLP subsystems for 2.6.28
 
sylaw@i2r.a-star.edu.sg wrote:
> 
>   I am currently working on trying to WUSB linux to work on DLINK
> dub1210 dongle. Does the 2.6.26-rc8 of WUSB UWB linux work with
> DUB1210, as when i try to connect to the DLINK UWB Hub it show me
> error when it try to enumerate the hub i believe. Your help is greatly
> appreciated ! thx in advance !

The WUSB hub (DWA) won't do anything useful because there's no DWA
driver.  However, you should be able to authenticate and enumerate it.

Could you expand on the error messages?  It may be useful to build the
driver with additional debugging.

David
-- 
David Vrabel, Senior Software Engineer, Drivers
CSR, Churchill House, Cambridge Business Park,  Tel: +44 (0)1223 692562
Cowley Road, Cambridge, CB4 0WZ                 http://www.csr.com/

**********************  ANNOUNCEMENT ********************************
 We have moved to Fusionopolis!
 Our official address is:
 Institute for Infocomm Research,  1 Fusionopolis Way,  #21-01 Connexis, South Tower,
 Singapore 138632.   Main line: +65 64082000. Main fax: +65 67761378
 Please visit http://www.fusionopolis.a-star.edu.sg/ for more information
 on Fusionopolis.
******************************************************************

Institute For Infocomm Research - Disclaimer This email is confidential and may be privileged.  If you are not the intended recipient, please delete it and notify us immediately. Please do not copy or use it for any purpose, or disclose its contents to any other person. Thank you."

^ permalink raw reply	[flat|nested] 5+ messages in thread

* RE: UWB, WUSB, and WLP subsystems for 2.6.28
  2008-10-23  9:00   ` UWB, WUSB, and WLP subsystems for 2.6.28 David Vrabel
  2008-10-24  2:13     ` Law Sie Yong
@ 2008-10-29  1:27     ` Law Sie Yong
  2008-10-29  2:05     ` Law Sie Yong
  2008-11-07  9:02     ` Law Sie Yong
  3 siblings, 0 replies; 5+ messages in thread
From: Law Sie Yong @ 2008-10-29  1:27 UTC (permalink / raw)
  To: David Vrabel; +Cc: Kernel development list

Hi David,

  As i look through the WUSB linux code, i couldnt seem to locate the code that append the UWB MAC layer header to the data frame of WUSB, or i might have missed it. To send out the WUSB data frame, does the code is expected to append the MAC header that indicate the EUI of dest and src, so the WUSB data frame can be sent correctly to the receiver, in this case dest EUI will be the HUB? Dlink DUB1210 spec said that its compliance to  MAC 1.0 which i believe the MAC header should contains the dest and src EUI for the data frame.

Law Sie Yong
Senior Research Officer
Communication Systems Department



-----Original Message-----
From: David Vrabel [mailto:david.vrabel@csr.com]
Sent: Thu 10/23/2008 5:00 PM
To: Law Sie Yong
Cc: Kernel development list
Subject: Re: UWB, WUSB, and WLP subsystems for 2.6.28
 
sylaw@i2r.a-star.edu.sg wrote:
> 
>   I am currently working on trying to WUSB linux to work on DLINK
> dub1210 dongle. Does the 2.6.26-rc8 of WUSB UWB linux work with
> DUB1210, as when i try to connect to the DLINK UWB Hub it show me
> error when it try to enumerate the hub i believe. Your help is greatly
> appreciated ! thx in advance !

The WUSB hub (DWA) won't do anything useful because there's no DWA
driver.  However, you should be able to authenticate and enumerate it.

Could you expand on the error messages?  It may be useful to build the
driver with additional debugging.

David
-- 
David Vrabel, Senior Software Engineer, Drivers
CSR, Churchill House, Cambridge Business Park,  Tel: +44 (0)1223 692562
Cowley Road, Cambridge, CB4 0WZ                 http://www.csr.com/

**********************  ANNOUNCEMENT ********************************
 We have moved to Fusionopolis!
 Our official address is:
 Institute for Infocomm Research,  1 Fusionopolis Way,  #21-01 Connexis, South Tower,
 Singapore 138632.   Main line: +65 64082000. Main fax: +65 67761378
 Please visit http://www.fusionopolis.a-star.edu.sg/ for more information
 on Fusionopolis.
******************************************************************

Institute For Infocomm Research - Disclaimer This email is confidential and may be privileged.  If you are not the intended recipient, please delete it and notify us immediately. Please do not copy or use it for any purpose, or disclose its contents to any other person. Thank you."

^ permalink raw reply	[flat|nested] 5+ messages in thread

* RE: UWB, WUSB, and WLP subsystems for 2.6.28
  2008-10-23  9:00   ` UWB, WUSB, and WLP subsystems for 2.6.28 David Vrabel
  2008-10-24  2:13     ` Law Sie Yong
  2008-10-29  1:27     ` Law Sie Yong
@ 2008-10-29  2:05     ` Law Sie Yong
  2008-11-07  9:02     ` Law Sie Yong
  3 siblings, 0 replies; 5+ messages in thread
From: Law Sie Yong @ 2008-10-29  2:05 UTC (permalink / raw)
  To: David Vrabel; +Cc: Kernel development list

Hi David,

  Attached below is the error msg i got when trying to enumerate the DLINK WUSB HUB


Oct 29 09:58:46 localhost kernel: wa_notif_dispatch: HWA_NOTIF_DN, device connect 
Oct 29 09:58:46 localhost kernel: #015<6>hwa-hc 1-1:1.0: DN CONNECT: device f9 0c a6 60 83 73 a6 59 c1 ca ed 1c 63 4d 45 9a @ 0 (self-beacon) wants to reconnect
Oct 29 09:58:46 localhost kernel: hwa-hc 1-1:1.0: Connecting new WUSB device to address 130, port 0
Oct 29 09:58:46 localhost kernel: __hwahc_op_dev_info_set: entry
Oct 29 09:58:46 localhost kernel: #015
Oct 29 09:58:46 localhost kernel: #015<6>hwa-hc 1-1:1.0: device 0: unauth addr 130
Oct 29 09:58:46 localhost kernel: wa_notif_dispatch: HWA_NOTIF_DN, device connect 
Oct 29 09:58:46 localhost kernel: #015<6>hwa-hc 1-1:1.0: DN CONNECT: device f9 0c a6 60 83 73 a6 59 c1 ca ed 1c 63 4d 45 9a @ 0 (self-beacon) wants to reconnect
Oct 29 09:58:46 localhost kernel: __ratelimit: 4 messages suppressed
Oct 29 09:58:46 localhost kernel: hwa-hc 1-1:1.0: Already handling dev f9 0c a6 60 83 73 a6 59 c1 ca ed 1c 63 4d 45 9a  (it might be slow)
Oct 29 09:58:46 localhost kernel: uwbd_dev_onair entry
Oct 29 09:58:46 localhost kernel: #015uwb_dev_add: device name is 00:21:91:1d:4e:c7
Oct 29 09:58:46 localhost kernel: #015uwb_dev f5a23800 parent_dev f6fcec18
Oct 29 09:58:46 localhost kernel: __uwb_dev_sys_add: dev name is 00:21:91:1d:4e:c7
Oct 29 09:58:46 localhost kernel: #015uwb_dev f5a23800 parent_dev f6fcec18) = 0
Oct 29 09:58:46 localhost kernel: uwb_rc uwb0: uwb device (mac 00:21:91:1d:4e:c7 dev 08:5f) connected to usb 1-1:1.1
Oct 29 09:58:46 localhost kernel: uwb_notify: called
Oct 29 09:58:46 localhost kernel: #015wa_notif_dispatch: HWA_NOTIF_BPST_ADJ 
Oct 29 09:58:46 localhost kernel: #015<3>hwa-hc 1-1:1.0: HWA: unknown notification 0x94, 3 bytes; discarding
Oct 29 09:58:46 localhost kernel: hwa-hc 1-1:1.0: 03 94 01 00 00 00 00 00 
Oct 29 09:58:46 localhost kernel: hwa-hc 1-1:1.0: 40 a7 fa f6 00 10 a4 f8 
Oct 29 09:58:46 localhost kernel: usb 6-1: new variable speed Wireless USB device using hwa-hc and address 2
Oct 29 09:58:46 localhost kernel: hwahc_op_urb_enqueue : entry 
Oct 29 09:58:46 localhost kernel: #015
Oct 29 09:58:46 localhost kernel: #015wa_urb_enqueue: endpoint address is 0
Oct 29 09:58:46 localhost kernel: #015
Oct 29 09:58:46 localhost kernel: #015
Oct 29 09:58:46 localhost kernel: #015wa_urb_enqueue: endpoint direction is out
Oct 29 09:58:46 localhost kernel: #015
Oct 29 09:58:46 localhost kernel: #015
Oct 29 09:58:46 localhost kernel: #015urb buffer is 80 3b 9c f5 2c 0 9 0 3 e fe 0 fe ff ff 0 8 20 f8 ff 0 ff 0 ff 0 ff 0 ff 0 ff 0 ff 0 ff 0 ff 0 ff 0 ff 0 ff 0 ff 0 ff 0 ff 0 ff 0 0 0 0 0 0 0 0 0 0 0 0 0 0 
Oct 29 09:58:46 localhost kernel: #015
Oct 29 09:58:46 localhost kernel: #015xfer f59c3b80 urb f59ad500 pipe 0x80000080 [64 bytes] nodma inbound inline
Oct 29 09:58:46 localhost kernel: wa_notif_dispatch: HWA_NOTIF_BPST_ADJ 
Oct 29 09:58:46 localhost kernel: #015<3>hwa-hc 1-1:1.0: HWA: unknown notification 0x94, 3 bytes; discarding
Oct 29 09:58:46 localhost kernel: hwa-hc 1-1:1.0: 03 94 01 00 00 00 00 00 
Oct 29 09:58:46 localhost kernel: hwa-hc 1-1:1.0: 40 a7 fa f6 00 10 a4 f8 
Oct 29 09:58:47 localhost kernel: wa_notif_dispatch: HWA_NOTIF_BPST_ADJ 
Oct 29 09:58:47 localhost kernel: #015<3>hwa-hc 1-1:1.0: HWA: unknown notification 0x94, 3 bytes; discarding
Oct 29 09:58:47 localhost kernel: hwa-hc 1-1:1.0: 03 94 01 00 00 00 00 00 
Oct 29 09:58:47 localhost kernel: hwa-hc 1-1:1.0: 44 2d 4c 69 6e 6b 00 00 
Oct 29 09:58:47 localhost kernel: wa_notif_dispatch: HWA_NOTIF_BPST_ADJ 
Oct 29 09:58:47 localhost kernel: #015<3>hwa-hc 1-1:1.0: HWA: unknown notification 0x94, 3 bytes; discarding
Oct 29 09:58:47 localhost kernel: hwa-hc 1-1:1.0: 03 94 01 00 00 00 00 00 
Oct 29 09:58:47 localhost kernel: hwa-hc 1-1:1.0: 44 2d 4c 69 6e 6b 00 00 
Oct 29 09:58:47 localhost kernel: wa_notif_dispatch: HWA_NOTIF_BPST_ADJ 
Oct 29 09:58:47 localhost kernel: #015<3>hwa-hc 1-1:1.0: HWA: unknown notification 0x94, 3 bytes; discarding
Oct 29 09:58:47 localhost kernel: hwa-hc 1-1:1.0: 03 94 01 00 00 00 00 00 
Oct 29 09:58:47 localhost kernel: hwa-hc 1-1:1.0: c0 58 9e f5 ff ff ff ff 
Oct 29 09:58:47 localhost kernel: wa_notif_dispatch: HWA_NOTIF_BPST_ADJ 
Oct 29 09:58:47 localhost kernel: #015<3>hwa-hc 1-1:1.0: HWA: unknown notification 0x94, 3 bytes; discarding
Oct 29 09:58:47 localhost kernel: hwa-hc 1-1:1.0: 03 94 01 00 00 00 00 00 
Oct 29 09:58:47 localhost kernel: hwa-hc 1-1:1.0: 80 54 9e f5 ff ff ff ff 
Oct 29 09:58:48 localhost kernel: wa_notif_dispatch: HWA_NOTIF_BPST_ADJ 
Oct 29 09:58:48 localhost kernel: #015<3>hwa-hc 1-1:1.0: HWA: unknown notification 0x94, 3 bytes; discarding
Oct 29 09:58:48 localhost kernel: hwa-hc 1-1:1.0: 03 94 01 00 00 00 00 00 
Oct 29 09:58:48 localhost kernel: hwa-hc 1-1:1.0: 40 ad df f6 00 f0 91 f8 
Oct 29 09:58:48 localhost kernel: wa_notif_dispatch: HWA_NOTIF_BPST_ADJ 
Oct 29 09:58:48 localhost kernel: #015<3>hwa-hc 1-1:1.0: HWA: unknown notification 0x94, 3 bytes; discarding
Oct 29 09:58:48 localhost kernel: hwa-hc 1-1:1.0: 03 94 01 00 00 00 00 00 
Oct 29 09:58:48 localhost kernel: hwa-hc 1-1:1.0: 80 52 9e f5 08 00 00 00 
Oct 29 09:58:48 localhost kernel: wa_notif_dispatch: HWA_NOTIF_BPST_ADJ 
Oct 29 09:58:48 localhost kernel: #015<3>hwa-hc 1-1:1.0: HWA: unknown notification 0x94, 3 bytes; discarding
Oct 29 09:58:48 localhost kernel: hwa-hc 1-1:1.0: 03 94 01 00 00 00 00 00 
Oct 29 09:58:48 localhost kernel: hwa-hc 1-1:1.0: 80 52 9e f5 08 00 00 00 
Oct 29 09:58:48 localhost kernel: wa_notif_dispatch: HWA_NOTIF_BPST_ADJ 
Oct 29 09:58:49 localhost kernel: #015wa_notif_dispatch: HWA_NOTIF_BPST_ADJ 
Oct 29 09:58:49 localhost kernel: #015wa_notif_dispatch: HWA_NOTIF_BPST_ADJ 
Oct 29 09:58:50 localhost kernel: #015wa_notif_dispatch: HWA_NOTIF_BPST_ADJ 
Oct 29 09:58:50 localhost kernel: #015uwb_notify: called
Oct 29 09:58:50 localhost kernel: #015<6> 00:21:91:1d:4e:c7: uwb device (mac 00:21:91:1d:4e:c7 dev 08:5f) disconnected from usb 1-1:1.1
Oct 29 09:58:50 localhost kernel:  00:21:91:1d:4e:c7: uwb_dev_sys_release: uwb_dev f5a23800 freed
Oct 29 09:58:51 localhost kernel: hwahc_op_urb_denqueue : entry 
Oct 29 09:58:51 localhost kernel: #015
Oct 29 09:58:51 localhost kernel: #015xfer f59c3b80#0 ABORTED: result -115

It seems that the DN_CONNECT go thru juzt fine, but when sending urb packet to enumerate the hub (i think ??), there is error in the function __wa_xfer_is_done, case WA_SEG_ABORTED, which cause the abort to occur.BTW, when sending data frame over WUSB to the HUB, just curious if the  endpoint address to be 01 for OUT, instead of 0 (default control endpoint) , as i printed out the value of endpoint address to be 0. thx again for your info !



Law Sie Yong
Senior Research Officer
Communication Systems Department



-----Original Message-----
From: David Vrabel [mailto:david.vrabel@csr.com]
Sent: Thu 10/23/2008 5:00 PM
To: Law Sie Yong
Cc: Kernel development list
Subject: Re: UWB, WUSB, and WLP subsystems for 2.6.28
 
sylaw@i2r.a-star.edu.sg wrote:
> 
>   I am currently working on trying to WUSB linux to work on DLINK
> dub1210 dongle. Does the 2.6.26-rc8 of WUSB UWB linux work with
> DUB1210, as when i try to connect to the DLINK UWB Hub it show me
> error when it try to enumerate the hub i believe. Your help is greatly
> appreciated ! thx in advance !

The WUSB hub (DWA) won't do anything useful because there's no DWA
driver.  However, you should be able to authenticate and enumerate it.

Could you expand on the error messages?  It may be useful to build the
driver with additional debugging.

David
-- 
David Vrabel, Senior Software Engineer, Drivers
CSR, Churchill House, Cambridge Business Park,  Tel: +44 (0)1223 692562
Cowley Road, Cambridge, CB4 0WZ                 http://www.csr.com/

**********************  ANNOUNCEMENT ********************************
 We have moved to Fusionopolis!
 Our official address is:
 Institute for Infocomm Research,  1 Fusionopolis Way,  #21-01 Connexis, South Tower,
 Singapore 138632.   Main line: +65 64082000. Main fax: +65 67761378
 Please visit http://www.fusionopolis.a-star.edu.sg/ for more information
 on Fusionopolis.
******************************************************************

Institute For Infocomm Research - Disclaimer This email is confidential and may be privileged.  If you are not the intended recipient, please delete it and notify us immediately. Please do not copy or use it for any purpose, or disclose its contents to any other person. Thank you."

^ permalink raw reply	[flat|nested] 5+ messages in thread

* RE: UWB, WUSB, and WLP subsystems for 2.6.28
  2008-10-23  9:00   ` UWB, WUSB, and WLP subsystems for 2.6.28 David Vrabel
                       ` (2 preceding siblings ...)
  2008-10-29  2:05     ` Law Sie Yong
@ 2008-11-07  9:02     ` Law Sie Yong
  3 siblings, 0 replies; 5+ messages in thread
From: Law Sie Yong @ 2008-11-07  9:02 UTC (permalink / raw)
  To: David Vrabel; +Cc: Kernel development list

Hi David,

  Just wondering if you know the email address of Ed Stock from Intel, as he seems to have the firmware that work with WLP according to the link below

http://www.spinics.net/lists/linux-usb/msg11640.html. Or anyone in the mailing list that can let me know. Thx in advance !


Law Sie Yong
Senior Research Officer
Communication Systems Department

**********************  ANNOUNCEMENT ********************************
 We have moved to Fusionopolis!
 Our official address is:
 Institute for Infocomm Research,  1 Fusionopolis Way,  #21-01 Connexis, South Tower,
 Singapore 138632.   Main line: +65 64082000. Main fax: +65 67761378
 Please visit http://www.fusionopolis.a-star.edu.sg/ for more information
 on Fusionopolis.
******************************************************************

Institute For Infocomm Research - Disclaimer This email is confidential and may be privileged.  If you are not the intended recipient, please delete it and notify us immediately. Please do not copy or use it for any purpose, or disclose its contents to any other person. Thank you."

^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2008-11-07  9:06 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <fa.s78bJIT7sRB89tYmSVZWUEBUq5k@ifi.uio.no>
     [not found] ` <6f3df9eb-5c1a-4ee1-a78f-7c0ff55a42fc@t18g2000prt.googlegroups.com>
2008-10-23  9:00   ` UWB, WUSB, and WLP subsystems for 2.6.28 David Vrabel
2008-10-24  2:13     ` Law Sie Yong
2008-10-29  1:27     ` Law Sie Yong
2008-10-29  2:05     ` Law Sie Yong
2008-11-07  9:02     ` Law Sie Yong

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).