On 20 Mar 2014, at 15:20, Daniel O'Connor docon...@gsoft.com.au wrote:
On 20 Mar 2014, at 15:10, Daniel O'Connor docon...@gsoft.com.au wrote:
#8 0x8070f932 in usb_ioctl (dev=value optimized out,
cmd=3222040644, addr=0xfe011fab8270 \001, fflag=value optimized out,
td=value
Hi,
Can you try to reproduce using the attached patch.
You need to manually add:
#define USB_BUS_EXPLORE_PROC(bus) ((bus)-explore_proc)
Because the patch is for -current.
Thank you for your bug report!
--HPS
___
freebsd-usb@freebsd.org mailing
On 03/20/14 14:26, Hans Petter Selasky wrote:
Hi,
Can you try to reproduce using the attached patch.
You need to manually add:
#define USB_BUS_EXPLORE_PROC(bus) ((bus)-explore_proc)
Because the patch is for -current.
Thank you for your bug report!
--HPS
FYI
On 10 Oct 2013, at 18:18, Hans Petter Selasky h...@bitfrost.no wrote:
On 10/10/13 09:38, Daniel O'Connor wrote:
On 10/10/2013, at 16:59, Hans Petter Selasky h...@bitfrost.no wrote:
The usb_fifo_* code handles all wakeups so I am not sure.
The usb_fifo code only will only do refcounting.
On 20 Mar 2014, at 15:10, Daniel O'Connor docon...@gsoft.com.au wrote:
#8 0x8070f932 in usb_ioctl (dev=value optimized out,
cmd=3222040644, addr=0xfe011fab8270 \001, fflag=value optimized out,
td=value optimized out)
at /local0/src/sys/dev/usb/usb_dev.c:1075
Sigh, I just
On 10/09/13 23:25, Daniel O'Connor wrote:
On 09/10/2013, at 22:43, Hans Petter Selasky h...@bitfrost.no wrote:
On 10/09/13 12:38, Daniel O'Connor wrote:
On 09/10/2013, at 20:59, Hans Petter Selasky h...@bitfrost.no wrote:
It is actually running r253505, sorry I should have mentioned that
On 10/10/2013, at 16:59, Hans Petter Selasky h...@bitfrost.no wrote:
It might under some circumstances but not directly.
It has 3 sub interfaces, if there is an error on one the the DAQ program
will call abort() which would result in FDs being closed.
However that sub interface does not
On 10/10/13 09:38, Daniel O'Connor wrote:
On 10/10/2013, at 16:59, Hans Petter Selasky h...@bitfrost.no wrote:
It might under some circumstances but not directly.
It has 3 sub interfaces, if there is an error on one the the DAQ program will
call abort() which would result in FDs being
On 10/10/2013, at 18:18, Hans Petter Selasky h...@bitfrost.no wrote:
If you use synchronous USB control requests, then those should always error
out.
Yes it is synchronous (uses usbd_do_request_flags).
The usb_fifo_* code handles all wakeups so I am not sure.
The usb_fifo code only will
On 10/09/13 12:04, Daniel O'Connor wrote:
Hi,
We have a custom Cypress FX2 based data acquisition card connected to a FreeBSD
9.2 system.
Today the device disconnected
Oct 9 03:24:11 juskym kernel: ugsio0: at uhub3, port 1, addr 3 (disconnected)
and then some time later we noticed the data
On 09/10/2013, at 20:59, Hans Petter Selasky h...@bitfrost.no wrote:
I have previously run the same hardware on 9.0 (where there was a panic in
devfs triggered if the DAQ card disconncted sometimes) and 9.1 (where I have
not seen any problems).
Does anyone have an idea about how I could
On 10/09/13 12:38, Daniel O'Connor wrote:
On 09/10/2013, at 20:59, Hans Petter Selasky h...@bitfrost.no wrote:
I have previously run the same hardware on 9.0 (where there was a panic in
devfs triggered if the DAQ card disconncted sometimes) and 9.1 (where I have
not seen any problems).
Does
On 09/10/2013, at 22:43, Hans Petter Selasky h...@bitfrost.no wrote:
On 10/09/13 12:38, Daniel O'Connor wrote:
On 09/10/2013, at 20:59, Hans Petter Selasky h...@bitfrost.no wrote:
It is actually running r253505, sorry I should have mentioned that before.
It isn't a serial device, although
13 matches
Mail list logo
