Am Freitag, 1. Juli 2005 07:42 schrieb oujin.rera:
> Hi
>
> I have a very basic question.
>
> I have written a Kernel driver for an USB device. Now I want to write an
> user space application to open the device and get the handle. What will the
> parameter(Path) to the "open" function in the use
Sorry My answer was not very clear
> You didn't answer my last question. If you run and exit from VMware, and
> then unplug and replug the device, does the driver work? Better yet, if
> you leave the device unplugged while running and exiting from VMware and
> then plug the device in afterw
Hi Oliver
Thanks for patience and time!
I would like to present my question in different way.
1) I have written a Kernel USB driver with open, ioctl , probe and
disconnect
2) Now i want to write an application above that. For example
main()
{
int file_desc, ret_val;
char *msg = "Message
Am Freitag, 1. Juli 2005 11:56 schrieb oujin.rera:
> In the above code "open" requires a file name. How do i find the name of the
> USB device along with the path ?
Normally you don't. You claim a range of minor numers in your driver
descriptor and use the corresponding device nodes.
HTH
Thanks again!
But when will "open method" of the driver be called !! Am I missing
something :-(
TIA
OuJin
- Original Message -
From: "Oliver Neukum" <[EMAIL PROTECTED]>
To: "oujin.rera" <[EMAIL PROTECTED]>
Cc:
Sent: Friday, July 01, 2005 5:36 PM
Subject: Re: [linux-usb-devel] opening a
Suppose my driver's probe method is called for a device,
some initialisation is done (eg: I change the altsetting),
but finally the probe fails. Will the device state be
reset in any way before other drivers are probed?
Thanks a lot,
Duncan.
Am Freitag, 1. Juli 2005 14:37 schrieb oujin.rera:
> Thanks again!
>
> But when will "open method" of the driver be called !! Am I missing
> something :-(
It is called when the syscall open() is called from user space.
Regards
Oliver
On Fri, 1 Jul 2005, Oliver Neukum wrote:
> Am Freitag, 1. Juli 2005 14:37 schrieb oujin.rera:
> > Thanks again!
> >
> > But when will "open method" of the driver be called !! Am I missing
> > something :-(
>
> It is called when the syscall open() is called from user space.
Oliver, you're missin
On Fri, 1 Jul 2005, Duncan Sands wrote:
> Suppose my driver's probe method is called for a device,
> some initialisation is done (eg: I change the altsetting),
> but finally the probe fails. Will the device state be
> reset in any way before other drivers are probed?
No. Do you think selecting
Hi Alan,
> > Suppose my driver's probe method is called for a device,
> > some initialisation is done (eg: I change the altsetting),
> > but finally the probe fails. Will the device state be
> > reset in any way before other drivers are probed?
>
> No. Do you think selecting altsetting 0 will r
On Thu, 30 Jun 2005, Matthias Urlichs wrote:
> > usb_disconnect does not disable the chip -- that happens after it returns.
> > The only way usb_disconnect interacts with the controller is through the
> > hcd_endpoint_disable routine. That in turn does a normal unlink (which
> > you say will no
On Fri, 1 Jul 2005, Duncan Sands wrote:
> Hi Alan,
>
> > > Suppose my driver's probe method is called for a device,
> > > some initialisation is done (eg: I change the altsetting),
> > > but finally the probe fails. Will the device state be
> > > reset in any way before other drivers are probed?
> > but do we want to guarantee that the altsetting is always zero
> > when probe is called (likewise for configuration)? After all, drivers
> > can be responsible for setting the values they want.
>
> I think we do. Drivers should find their devices initially in the
> default state. That's wh
Hi,
Alan Stern:
> I get it. And that call to finish_unlinks is made from within the
> ohci_endpoint_disable routine. It looks like the "clean up the list
> without looking at the hardware state" happens only when the HC isn't
> running.
Right.
> But during a normal rmmod the HC _is_ running.
On Fri, 1 Jul 2005, Duncan Sands wrote:
> > > but do we want to guarantee that the altsetting is always zero
> > > when probe is called (likewise for configuration)? After all, drivers
> > > can be responsible for setting the values they want.
> >
> > I think we do. Drivers should find their de
Hi Alan,
> ? You sound confused.
seems so :)
> Configurations aren't changed as easily as altsettings. They can't be
> changed at all by drivers, normally. Remember, each configuration
> contains a set of interfaces, and drivers bind to interfaces. Change the
> config and you've got a com
On Fri, 1 Jul 2005, Matthias Urlichs wrote:
> > But during a normal rmmod the HC _is_ running. So how does this
> > end up solving your problem? Does ohci-hcd somehow learn that the
> > controller is _not_ running?
> >
> During a normal rmmod the HC is running; however, PCMCIA is special in
> t
Am Freitag, 1. Juli 2005 16:28 schrieb Duncan Sands:
> > > but do we want to guarantee that the altsetting is always zero
> > > when probe is called (likewise for configuration)? After all, drivers
> > > can be responsible for setting the values they want.
> >
> > I think we do. Drivers should f
Thanks!
Yes that is my question! What will be the parameter for syscall open(). How
will i get path of the USB device dynamically ?
TIA
OuJin
- Original Message -
From: "Oliver Neukum" <[EMAIL PROTECTED]>
To: "oujin.rera" <[EMAIL PROTECTED]>
Cc:
Sent: Friday, July 01, 2005 6:57 PM
Su
Am Freitag, 1. Juli 2005 17:58 schrieben Sie:
> Thanks!
>
> Yes that is my question! What will be the parameter for syscall open(). How
> will i get path of the USB device dynamically ?
If you absolutely insist on doing this dynamically, you should run hald
and query it via D-BUS. This question i
As the subject says: why is there no usb_fill_iso_urb
helper routine? I was looking around to see how various
drivers handle iso urb initialisation, and I noticed (for
example) that some of them don't initialise urb->lock...
Well, maybe it doesn't need to be initialised for iso urbs,
or maybe it d
El Lunes, 27 de Junio de 2005 19:27, randy_dunlap escribió:
> On Mon, 27 Jun 2005 19:19:56 -0500 Gustavo Guillermo Pérez wrote:
> | El Jueves, 23 de Junio de 2005 23:51, randy_dunlap escribió:
> | > On Sat, 18 Jun 2005 11:52:53 -0500 Gustavo Guillermo Pérez wrote:
> | > | El Viernes, 17 de Junio de
For a driver for a USB ISDN device I help maintaining
(http://gigaset307x.sourceforge.net - not yet submitted for
inclusion in the kernel, for the obvious reasons), I have
received a problem report that on Ubuntu with kernel 2.6.10,
the setup is lost on every reboot. (Details at
https://sourceforge
23 matches
Mail list logo
