On 4/3/07, Hans Petter Selasky [EMAIL PROTECTED] wrote:
On Tuesday 03 April 2007 13:27, Xiaofan Chen wrote:
I was redirected to this list as per the suggestion from the
libusb mailing list.
It will be greatly appreciated that someone can suggest
how to debug this problem?
With the new USB
On 4/4/07, Hans Petter Selasky [EMAIL PROTECTED] wrote:
On Wednesday 04 April 2007 01:55, Xiaofan Chen wrote:
On 4/3/07, Hans Petter Selasky [EMAIL PROTECTED] wrote:
Hi,
I think that your device is broken, and goes bad when it receives a
clear-stall request for the interrupt pipe
On 4/4/07, Hans Petter Selasky [EMAIL PROTECTED] wrote:
On Wednesday 04 April 2007 01:55, Xiaofan Chen wrote:
On 4/3/07, Hans Petter Selasky [EMAIL PROTECTED] wrote:
Hi,
I think that your device is broken, and goes bad when it receives a
clear-stall request for the interrupt pipe
On 7/8/07, Xiaofan Chen [EMAIL PROTECTED] wrote:
On 7/8/07, M. Warner Losh [EMAIL PROTECTED] wrote:
In message: [EMAIL PROTECTED]
Xiaofan Chen [EMAIL PROTECTED] writes:
: On 7/5/07, Hans Petter Selasky [EMAIL PROTECTED] wrote:
: The chip does not handle a clear-stall request
to FIFO.
Clear interrupt endpoint stall.
There is no data to read, because the FIFO has been emptied as a part of the
stall command.
Xiaofan Chen: Could you check the datasheet for the chip that is used, what
the stall command actually does?
I need to look further but what you mentioned seem
On 7/9/07, Pierre-Luc Drouin [EMAIL PROTECTED] wrote:
I have looked through the GPSBabel code and it looks like it is failing at the
very first call of usb_bulk_write() when the initialization packet is sent to
the device.
Is this a known bug with libusb on FreeBSD 6.2?
Maybe you can try
to FIFO.
Clear interrupt endpoint stall.
There is no data to read, because the FIFO has been emptied as a part of the
stall command.
Xiaofan Chen: Could you check the datasheet for the chip that is used, what
the stall command actually does?
Sorry that I have three more questions:
1) What
On 7/15/07, Hans Petter Selasky [EMAIL PROTECTED] wrote:
2) For the host, how does it know that the buffer data is still correct if
the buffer is not cleared?
Clear stall should only clear the data toggle!
You need a second control command to reset the buffers and/or the protocol!
2)
On 8/10/07, Robert Cousins [EMAIL PROTECTED] wrote:
Hello:
I've got several USB devices which I'd like to talk to from a program.
They are Phigets -- a servo controller, an RFID reader, etc.
Could someone please give me a hint as to the best starting point
for learning
how to use
On 7/9/07, M. Warner Losh [EMAIL PROTECTED] wrote:
I need to look it up, but I believe that a clear endpoint stall also
resets the toggle, and that was the bug that was tracked down.
Remind me when is this clear endpoint stall sent? In 7.x we don't
send one on pipe open unless the device is
On 9/29/07, Chuck T. [EMAIL PROTECTED] wrote:
I have a Linux application that talks to an USB audio dongle
that I'm trying to port to FreeBSD. I have no problem with the
audio portion, but I'm also trying to use libusb to access the
GPIO bits on the chip.
What is the Linux application? How
On 9/29/07, Chuck T. [EMAIL PROTECTED] wrote:
I think your device is a USB composite USB device with two
interfaces (one for USB audio and the other for GPIO). How
do you control the GPIO under Linux (by control transfer
or interrupt/bulk transfer)? If the Linux application indeed
works at
On 9/29/07, Chuck T. [EMAIL PROTECTED] wrote:
if(dev != NULL) {
if((udev = usb_open(dev)) != NULL) {
Ret = 0;
}
Hmm, you do not set USB configurations. I know this might
be good for Linux but this will not work under Windows.
Not so sure about FreeBSD.
I have tested
Somehow the vendor ID is parsed wrongly. 0x04d8 is for Microchip technology.
===[mcuee] ~/Desktop/build/fsusb/fsusb-0.1.11-2 # sudo usbdevs -v
Controller /dev/usb1:
addr 126: full speed, power 100 mA, config 1, product 0x000b(0x000b),
I-Tuner Networks(0x04d8), rev 0.00
port 4 addr 126: full
I am trying to get the PICDEM FS USB demo board working under
FreeBSD. There are two libusb based application for it which work
under Linux and Windows. I am now trying to get the bootloader
working first. It is not working. Possibly this is again a firmware bug
related issue but I would like to
I have updated the kernel and the new HPD stack and now
PICkit 2 is again not working. I have updated the firmware
based on the newly released Microchip stack and I thought
I solved the data toggle problem by changing a line as
suggested by Leo Bodnar.
On 10/13/07, Hans Petter Selasky [EMAIL PROTECTED] wrote:
I think that the write STALLED. You can check this by turning on
debugging on the OHCI controller by:
systctl hw.usb.ohci.debug=15
Replace ohci by ehci or uhci if you are using such controllers.
Strange today reading seems to work. I
On 10/13/07, Hans Petter Selasky [EMAIL PROTECTED] wrote:
Resource temporarily unavailable maps to EAGAIN
according to man errno. From what I can see from the log
you have provided this means that the msleep()
call in ugenread timed out.
What timeout have you programmed in your PICkit ?
It
Today I checked the Demo mode of PICDEM FS USB demo board.
it does not work either. Again this uses interrupt transfer.
===[mcuee] ~/Desktop/build/pyusb-0.4.1/samples # sudo ./usbenum.py
Device: /dev/ugen0
Device class: 0
Device sub class: 0
Device protocol: 0
Max packet size: 8
On 10/13/07, Hans Petter Selasky [EMAIL PROTECTED] wrote:
What timeout have you programmed in your PICkit ?
It is 1000ms. I change it to 1ms but this does not help.
Do you see that the code is waiting 10 seconds for the timeout ?
I think so. The program stops quite a while before
On 10/13/07, Xiaofan Chen [EMAIL PROTECTED] wrote:
Oops, the original code is using bulk transfer. I changed it to interrupt
transfer but the error is the same.
===[mcuee] ~/Desktop/build/fsusb/Demo # sudo ./fsusb_demo
Locating Microchip(tm) PICDEM(tm) FS USB Demo Board (vendor
0x04d8
On 10/16/07, Hans Petter Selasky [EMAIL PROTECTED] wrote:
On Saturday 13 October 2007, Xiaofan Chen wrote:
On 10/13/07, Hans Petter Selasky [EMAIL PROTECTED] wrote:
Resource temporarily unavailable maps to EAGAIN
according to man errno. From what I can see from the log
you have
On 10/13/07, Xiaofan Chen [EMAIL PROTECTED] wrote:
Today I checked the Demo mode of PICDEM FS USB demo board.
it does not work either. Again this uses interrupt transfer.
This is with the latest HPS USB stack and 6.2 Stable.
On 10/16/07, Hans Petter Selasky [EMAIL PROTECTED] wrote
On 10/13/07, Xiaofan Chen [EMAIL PROTECTED] wrote:
On 10/13/07, Hans Petter Selasky [EMAIL PROTECTED] wrote:
I think that the write STALLED. You can check this by turning on
debugging on the OHCI controller by:
systctl hw.usb.ohci.debug=15
Replace ohci by ehci or uhci if you are using
On 10/17/07, Hans Petter Selasky [EMAIL PROTECTED] wrote:
Thanks a lot. So it seems there is still a bug in the firmware. Maybe two.
The first one caused the stall (why?). The second one is still related to
dealing with clear stall feature reques
I think that the clear-stall command will
OpenUSB's API is now rather stable and they have the front end
and Linux/Solaris backend basically done. It is a fork of libusb-1.0
development branch since that branch is dormant for a while.
The aim is to be thread safe and supports assync I/O and isochronous
transfer where libusb-0.1 may have
On 11/12/07, Henrik Brix Andersen [EMAIL PROTECTED] wrote:
Is it possible for some people here to implement a backend
(based on ugen?) for FreeBSD?
Interesting - definitely something I will take a look at. Thank you
for the pointer.
Or maybe at least improve the current libusb-0.1.x
On Nov 17, 2007 4:38 PM, Hans Petter Selasky [EMAIL PROTECTED] wrote:
Could you be a bit more specific? I know there are some missing calls
in FreeBSD. And I have problems with libusb interrupt write with the
default kernel (hangs). It is documented here.
On Nov 17, 2007 7:31 PM, Hans Petter Selasky [EMAIL PROTECTED] wrote:
On Saturday 17 November 2007, Xiaofan Chen wrote:
On Nov 17, 2007 4:38 PM, Hans Petter Selasky [EMAIL PROTECTED] wrote:
Could you be a bit more specific? I know there are some missing calls
in FreeBSD. And I have
On Jan 10, 2008 2:34 AM, Hans Petter Selasky [EMAIL PROTECTED] wrote:
On Wednesday 09 January 2008, Mikhail Teterin wrote:
We really need the low-level (ugen?) interfaces available for all
USB-devices -- even those, which are /also/ handled by higher-level
interfaces (like ulpt, uscan,
On Thu, Apr 24, 2008 at 10:59 PM, Xiaofan Chen [EMAIL PROTECTED] wrote:
[EMAIL PROTECTED] /var/crash]# ls -la
total 508352
drwxr-x--- 2 root wheel512 Apr 24 22:07 .
drwxr-xr-x 25 root wheel512 Apr 25 06:07 ..
-rw-r--r-- 1 root wheel 2 Apr 24 22:07 bounds
On Thu, Apr 24, 2008 at 11:21 PM, Hans Petter Selasky [EMAIL PROTECTED] wrote:
I have fixed some issues where the Giant lock was not locked when calling
into
the USB stack recently. What version are you at? A stack backtrace from the
panic would also be nice. Make sure that everything is
On Tue, Oct 16, 2007 at 9:34 PM, Xiaofan Chen [EMAIL PROTECTED] wrote:
On 10/13/07, Xiaofan Chen [EMAIL PROTECTED] wrote:
On 10/13/07, Hans Petter Selasky [EMAIL PROTECTED] wrote:
I think that the write STALLED. You can check this by turning on
debugging on the OHCI controller
On Fri, Apr 25, 2008 at 7:34 AM, Xiaofan Chen [EMAIL PROTECTED] wrote:
On Thu, Apr 24, 2008 at 11:57 PM, Hans Petter Selasky [EMAIL PROTECTED]
wrote:
The problem should at least be fixed in revision 711. The problem has
existed for a while after I made some changes
I've got a free USB flash disk from National Semiconductor. It may
be the so-called U3 device since it comes up as a CDROM and
a removable USB drive. The removable USB drive part works fine.
But I am not able to mount the CD part which contains some datasheets
from National Semiconductor. Any tips
On Sat, Apr 26, 2008 at 5:54 AM, Hans Petter Selasky [EMAIL PROTECTED] wrote:
On Friday 25 April 2008, Xiaofan Chen wrote:
This does not work either with 7.0-Release and the HPS USB stack.
I will update to the latest SVN version of the HPS stack and see if the
situation will improve
On Sat, Apr 26, 2008 at 12:46 PM, Xiaofan Chen [EMAIL PROTECTED] wrote:
On Sat, Apr 26, 2008 at 11:50 AM, Xiaofan Chen [EMAIL PROTECTED] wrote:
2) Patch /sys/dev/usb/ugen.c
Change all lines looking like the following, that are not in a function
named xxx_callback
On Sat, Apr 26, 2008 at 5:49 AM, Hans Petter Selasky [EMAIL PROTECTED] wrote:
On Friday 25 April 2008, Xiaofan Chen wrote:
I've got a free USB flash disk from National Semiconductor. It may
be the so-called U3 device since it comes up as a CDROM and
a removable USB drive. The removable
On Sat, Apr 26, 2008 at 3:19 PM, Xiaofan Chen [EMAIL PROTECTED] wrote:
Since I have some other mass storage device and it seems
the latest HPS stack works fine with the normal ones (Kingston
Data Traveler 256MB, IMation 1GB Flash Drive and Nokia
6280 with 1GB MicroSD card in storage mode
On Mon, Apr 28, 2008 at 4:37 PM, Hans Petter Selasky [EMAIL PROTECTED] wrote:
Maybe this is a stupid question but how do I compile ugen only and not
the whole kernel?
You can get ugen alone by using loading the ugen module:
kldload ugen
kldunload ugen
I know this one. Actually my
On Mon, Apr 28, 2008 at 4:52 PM, Hans Petter Selasky [EMAIL PROTECTED] wrote:
I found it:
Edit /sys/dev/usb/ucycom.c and change:
--- src/sys/dev/usb/ucycom.c(revision 711)
+++ src/sys/dev/usb/ucycom.c(working copy)
@@ -167,8 +167,8 @@
};
DRIVER_MODULE(ucycom, uhub,
On Mon, Apr 28, 2008 at 4:35 PM, Hans Petter Selasky [EMAIL PROTECTED] wrote:
Then try to mount again. You can also try loading ata-usb instead of
umass. ata-usb will query the disk size regularly.
Hmm, I do not see any thing similar to ata-usb module in the kernel and
I can
On Tue, Apr 29, 2008 at 3:01 PM, Hans Petter Selasky [EMAIL PROTECTED] wrote:
If umass is in the kernel you need to rebuild. Else you kldunload umass.
I managed to crash the system again when playing with
kldload umass and kldunload umass. But maybe the
backtrace does not make much sense, to
On Tue, Apr 29, 2008 at 7:59 PM, Xiaofan Chen [EMAIL PROTECTED] wrote:
One more MP3 player which works under Windows XP and Linux but not
FreeBSD 7.0-Release with HPS stack.
[EMAIL PROTECTED] ~]# dmesg
...
umass1: vendor 0x10d6 USB 2.0(HS) Flash Disk, class 0/0, rev
2.00/1.00, addr 3 on usb2
On Wed, Apr 30, 2008 at 3:59 AM, Hans Petter Selasky [EMAIL PROTECTED] wrote:
Maybe you can get my USB stack working on your PIC board? It now supports the
Device Side aswell as the host side! See usbd_handle_request in:
On Wed, Apr 30, 2008 at 3:45 AM, Hans Petter Selasky [EMAIL PROTECTED] wrote:
As for the generic CDC-ACM device (the Olimex LPC-P2148), I do not know
how to load the necessary kernel module to get it work as a usb-serial
device.
Under Linux, there is a generic cdc-acm device
On Thu, May 1, 2008 at 12:33 AM, Hans Petter Selasky [EMAIL PROTECTED] wrote:
Hi,
Edit /sys/dev/usb/ugensa.c and add the VID+PID to the ugensa_devs
structure. Recompile the ugensa module (/sys/module/ugensa) and load it.
Thanks. Again there is an error.
ugensa0: LPCUSB USBSerial, class
On Thu, May 1, 2008 at 12:30 AM, Hans Petter Selasky [EMAIL PROTECTED] wrote:
Try and find out. I know that many structures can be optimized for minimal
memory usage. Currently I reserve space for 128 USB devices and 32 endpoints
and interfaces. If you reduce those numbers then you will save
On Sat, Apr 26, 2008 at 4:16 PM, Xiaofan Chen [EMAIL PROTECTED] wrote:
CP210x seems to be only supported by 8-Current. But maybe this
can be ported to the HPS stack.
Actually it is supported by the HPS stack with uslcom. I just found it today.
[EMAIL PROTECTED] ~]# dmesg
uslcom0: Silicon
On 6/9/08, Hans Petter Selasky [EMAIL PROTECTED] wrote:
There will soon be a utility that can do this, so that you can run:
usbconfig -u ugen0 -c 1
for example to select configuration index 1 for your device. Please note that
there will be one ugen device for every USB device present in the
On Sat, Jul 5, 2008 at 5:39 AM, Luigi Rizzo [EMAIL PROTECTED] wrote:
What about flow control? Is flow control required for these devices?
the ones I am talking about don't implement any form of flow control.
I suppose they would otherwise match the previous check.
They are many of this
On Fri, May 7, 2010 at 9:27 PM, Bernd Walter ti...@cicely7.cicely.de wrote:
I am guessing the program would need to be re-written to use v1.0
? Thanks for the feedback and help as always!
I recently converted own code to 1.0 API, just to get negative
feedback from Debian users, since they
On Fri, May 7, 2010 at 9:52 PM, Xiaofan Chen xiaof...@gmail.com wrote:
On Fri, May 7, 2010 at 4:40 AM, Hans Petter Selasky hsela...@c2i.net wrote:
The FreeBSD LibUSB v0.1 reports the wrong number of busses and devices. I can
fix this.
I've made a small patch, but it won't fix your issue
On Fri, Jun 11, 2010 at 2:43 PM, Mikhail T. mi+t...@aldan.algebra.com wrote:
I have linuxulator in the kernel (option COMPAT_LINUX), however, so, I
thought, it is supposed to just work... But it does not. Is anyone
successful getting skype with video on FreeBSD?
If that would work, it will
On Fri, Jun 1, 2012 at 9:45 PM, Engineering e...@athyriogames.com wrote:
I had been researching libusb for a while, but their webpage says it is not
recommended for HID devices and to use HIDAPI, which does not seem to be on
BSD.
HIDAPI does work under FreeBSD using libusb (1.0 API) as the
On Sat, Nov 17, 2012 at 8:19 PM, Hans Petter Selasky hsela...@c2i.net wrote:
On Friday 16 November 2012 23:47:29 Wojciech A. Koszek wrote:
Number: 173666
Category: usb
Synopsis: [USB, LIBUSB] usb_reset() behavior different between
GNU/Linux and FreeBSD Confidential: no
On Fri, Dec 21, 2012 at 3:38 PM, Hans Petter Selasky hsela...@c2i.net wrote:
If you look in the old libusb-0.1 code you'll see something different I think.
Could you check that?
Not much differences in reality. I believe it is a document bug for the
libusb-0.1.
Both old libusb-0.1 code and
On Sun, Dec 23, 2012 at 5:40 PM, Hans Petter Selasky hsela...@c2i.net wrote:
On Saturday 22 December 2012 11:17:15 Xiaofan Chen wrote:
On Fri, Dec 21, 2012 at 3:38 PM, Hans Petter Selasky hsela...@c2i.net
wrote:
If you look in the old libusb-0.1 code you'll see something different I
think
On Mon, Dec 24, 2012 at 9:17 AM, Xiaofan Chen xiaof...@gmail.com wrote:
On Sun, Dec 23, 2012 at 5:40 PM, Hans Petter Selasky hsela...@c2i.net wrote:
On Saturday 22 December 2012 11:17:15 Xiaofan Chen wrote:
On Fri, Dec 21, 2012 at 3:38 PM, Hans Petter Selasky hsela...@c2i.net
wrote:
If you
On Thu, Feb 21, 2013 at 1:04 AM, Hans Petter Selasky hsela...@c2i.net wrote:
USE_LIBUSB1 should be set, and -lusb must be used as linker flag, not -
lusb-1.0 like under linux.
In FreeBSD -lusb is a multi-API library, including v0.1, v1.0 and v2.0. Header
files are in /usr/include
Maybe it is
On Fri, Feb 22, 2013 at 4:15 PM, Boris Samorodov b...@passap.ru wrote:
USE_LIBUSB1 should be set, and -lusb must be used as linker flag, not -
lusb-1.0 like under linux.
After a deeper look at the code I realised that actually the called
LIBUSB1 is a USB-1.0 with some changes. The author call
61 matches
Mail list logo
