eneric devices ("handled by the ugen driver"). I need a mechanism that
> > will allow me to detach any device specific drivers that are attached to
> > a device and attach the ugen driver instead. I want to do this without
> > re-compiling the FreeBSD Kernel. Thanks in adv
On 05/09/2011, at 23:10, Daniel Grech wrote:
> Hi, I'm using libusb to gain access to raw USB Data from userspace. My
> problem is that this library only works with devices which are treated as
> generic devices ("handled by the ugen driver"). I need a mechanism that will
On Monday 05 September 2011 15:40:44 Daniel Grech wrote:
> Hi, I'm using libusb to gain access to raw USB Data from userspace. My
> problem is that this library only works with devices which are treated as
> generic devices ("handled by the ugen driver"). I need a mechanism
Hi, I'm using libusb to gain access to raw USB Data from userspace. My
problem is that this library only works with devices which are treated as
generic devices ("handled by the ugen driver"). I need a mechanism that will
allow me to detach any device specific drivers that are attac
at 6:47 PM, Dan Nelson wrote:
> In the last episode (Nov 13), Christopher Bowman said:
> > I have a Xilinx PCIe card installed in my machine and it appears that
> > ugen0 is claiming it. Why would a PCIe device even be offered to ugen?
> >
> > The message I get on boot
In the last episode (Nov 13), Christopher Bowman said:
> I have a Xilinx PCIe card installed in my machine and it appears that
> ugen0 is claiming it. Why would a PCIe device even be offered to ugen?
>
> The message I get on boot up is:
> ugen0 on uhub3
> Any way I can prevent
I have a Xilinx PCIe card installed in my machine and it appears that ugen0
is claiming it. Why would a PCIe device even be offered to ugen?
The message I get on boot up is:
ugen0 on uhub3
Any way I can prevent this so my on kld driver can attach?
Regards
Christopher
On Fri, 8 Sep 2006 02:53:26 -0400
Anish Mistry <[EMAIL PROTECTED]> wrote:
> On Thursday 07 September 2006 21:47, Z.C.B. wrote:
> > Any suggestions on reading or the like for talking to a ugen
> > device?
> read() and write() work. See the manpage to more options.
C
On Fri, 8 Sep 2006 06:43:51 +0200
Ed Schouten <[EMAIL PROTECTED]> wrote:
> * Z.C.B. <[EMAIL PROTECTED]> wrote:
> > Any suggestions on reading or the like for talking to a ugen
> > device?
>
> Well, I'm using ugen to test the workings of an Xbox 360 heads
* Z.C.B. <[EMAIL PROTECTED]> wrote:
> Any suggestions on reading or the like for talking to a ugen device?
Well, I'm using ugen to test the workings of an Xbox 360 headset. I just
use this:
$ cat /dev/ugen0.3 > myvoice
^C
$ cat myvoice > /dev/ugen0.4
Gives me back my voic
On Thursday 07 September 2006 21:47, Z.C.B. wrote:
> Any suggestions on reading or the like for talking to a ugen
> device?
read() and write() work. See the manpage to more options.
--
Anish Mistry
pgpsoCsEITTGg.pgp
Description: PGP signature
Any suggestions on reading or the like for talking to a ugen device?
signature.asc
Description: PGP signature
On Thu, Oct 07, 2004 at 04:22:12PM +0300, Niki Denev wrote:
> Bernd Walter writes:
> >On Wed, Oct 06, 2004 at 03:30:05PM +0300, Niki Denev wrote:
> >If you already an interface driver atatched then ugen fails to attach
> >the whole device.
>
> well, i think that this
y one ucom(4).
and if i plug the phone without any u* modules loaded the kernel attaches
ugen0 only.
>From what i understand it attaches the ugen0 using the info in the first
interface descriptor in the device.
Wouldn't it be more usefull for the kernel to attach ugen for every unknown
i
gt; interface descriptor in the device.
> > Wouldn't it be more usefull for the kernel to attach ugen for every unknown
> > interface in a device.
> > For example when attaching the phone with umodem loaded, i will get
> > the ucom(4) device and the other unrecognised i
d if i plug the phone without any u* modules loaded the kernel attaches
> ugen0 only.
> >From what i understand it attaches the ugen0 using the info in the first
> interface descriptor in the device.
> Wouldn't it be more usefull for the kernel to attach ugen for every unknown
&g
umodem and plug the phone it detects only one ucom(4).
> and if i plug the phone without any u* modules loaded the kernel attaches
> ugen0 only.
> >From what i understand it attaches the ugen0 using the info in the first
> interface descriptor in the device.
> Wouldn't it
aches
ugen0 only.
From what i understand it attaches the ugen0 using the info in the first
interface descriptor in the device.
Wouldn't it be more usefull for the kernel to attach ugen for every unknown
interface in a device.
For example when attaching the phone with umodem loaded, i will ge
On 15-Jul-2003 Martin wrote:
> On Tue, 2003-07-15 at 09:04, Terry Lambert wrote:
>> The attach should have failed, if it didn't have an interrupt.
>
> Somehow uhci0 didn't have interrupt, but it managed to find the webcam
> on ugen0. Don't ask me why. I have attached my logs below.
> You can see
On Tue, 2003-07-15 at 09:04, Terry Lambert wrote:
> The attach should have failed, if it didn't have an interrupt.
Somehow uhci0 didn't have interrupt, but it managed to find the webcam
on ugen0. Don't ask me why. I have attached my logs below.
You can see many devices sharing same irq. I don't kn
Martin wrote:
> Seems it was my fault. I found a solution in forums. I had to try
> out many things until someone has pointed me to BIOS settings and
> "assigning interrupt to USB". I noticed it was off and enabled it.
> It works now. :)
>
> (E.a.: no delays while accessing ugen0 and no freeze wit
Hi again,
Seems it was my fault. I found a solution in forums. I had to try
out many things until someone has pointed me to BIOS settings and
"assigning interrupt to USB". I noticed it was off and enabled it.
It works now. :)
(E.a.: no delays while accessing ugen0 and no freeze with X11.)
Mart
Hi all,
I have started to write a small video capture application for my webcam
(the first few steps). I am using /dev/ugen0 to talk to the webcam and
it seems to work. I can reset the webcam and hear a beep. It is correct
so far.
The problem is, I can only start my application on the text termin
escriptor:
> bLength=7 bDescriptorType=endpoint(5) bEndpointAddress=1-in
> bmAttributes=interrupt wMaxPacketSize=16 bInterval=10
This one and the following endpoints are for interface 1.
This is an alternate Interface, which means, that you can either use
this or another interface - ther
On Thu, 12 Jun 2003, Bernd Walter wrote:
> Not all endpoints have to be available in the current configuration.
> If you show me the output for your device I can tell you what is
> available under which condition.
Thanks, output below.
Andrew
--
DEVICE addr 2
DEVICE descriptor:
bLength=18 bD
On Thu, Jun 12, 2003 at 11:30:28PM +1000, Andrew wrote:
> On Sun, 8 Jun 2003, Bernd Walter wrote:
> > If you have no /dev/ugen?.? then the device has no other endpoints in
> > its current configuration.
> > The usbctl tool mentioned above is good to check devices about t
On Sun, 8 Jun 2003, Bernd Walter wrote:
> But there is lot of sample code available.
Thanks I'll take a look at that.
> You must be doing something wrong - the values are 16bit only.
Ooops...quite right. My mistake.
> If you have no /dev/ugen?.? then the device has no othe
On Mon, Jun 09, 2003 at 12:19:01AM +1000, Andrew wrote:
> Hi,
>
> I'm just having a look at ugen, trying to see if I can get any action out
> of a USB-serial converter that has no existing driver. This is my first
> foray into the USB world so I apologise for any stupid ques
Hi,
I'm just having a look at ugen, trying to see if I can get any action out
of a USB-serial converter that has no existing driver. This is my first
foray into the USB world so I apologise for any stupid questions...is
there a good tutorial somewhere?
To find my device I open /dev/ugen
That was it. Thank you.
Regards,
-Srinivas
>From: Ian Dowse <[EMAIL PROTECTED]>
>To: Srinivas Dharmasanam <[EMAIL PROTECTED]>
>CC: [EMAIL PROTECTED], [EMAIL PROTECTED]
>Subject: Re: hot swap with ugen
>Date: Wed, 21 Nov 2001 10:44:24 +
>
>In mess
In message <[EMAIL PROTECTED]>, Srinivas Dharmasanam writ
es:
>Hi,
>I'm using the generic usb device drive ugen for controlling a USB device.
>The problem is I'm having to reboot the computer each time I
>disconnect/connect the device in order for FreeBSD to see the
Hi,
I'm using the generic usb device drive ugen for controlling a USB device.
The problem is I'm having to reboot the computer each time I
disconnect/connect the device in order for FreeBSD to see the USB device.
Is there something specific I need to do with ugen driver to support
Hi,
Where (besides ugen.c) can I find some information about generic USB
devices aka ugen?
There's usb(3), but it only talks about hid devices.
--Roman Shterenzon, UNIX System Administrator and Consultant
[ Xpert UNIX Systems Ltd., Herzlia, Israel. Tel: +972-9-9522361 ]
To Unsubscribe:
How accurately does the NetBSD ugen(4) manual page describe FreeBSD's
ugen(4)? If it's accurate as it is, or can easily be fixed (any
volunteers?), I think we should just take it. :-) Perhaps my removing of
the .Xr ugen 4 from usb(4) was a bit premature... never mind.
http://www.FreeB
34 matches
Mail list logo
