On Thu, Jun 14, 2001 at 11:48:02PM +0200, Wolfgang Mües wrote:
> So if I see "300" as a value for timeout as an argument of
> usb_control_msg() [as in dabusb.c and dsbr100.c],
> this will mean different times on different platforms... ummpf!
Ooops, I will change that...
--
Georg Ache
> So if I see "300" as a value for timeout as an argument of
> usb_control_msg() [as in dabusb.c and dsbr100.c],
> this will mean different times on different platforms... ummpf!
This is why you will often see
foo_with_delay(xyz, HZ/5)
type stuff. (and on almost all platforms HZ is a
On Thursday, 14. June 2001 21:01, Alan Cox wrote:
> > I do this with intention: *you* as an old-fashioned linux
> > programmer - and many other here on the net - is knowing
> > very well what a "jiffie" is.
>
> 1/HZ of a second. Where HZ is a preprocessor constant dependant on
> platform, cpu and
On Thursday, 14. June 2001 21:14, Oliver Neukum wrote:
> > The word "jiffies" is totally meaningless to me.
>
> A jiffy is indeed the Linuxian equivalent of a tick.
> Its length is dependent on the architecture.
> On Alpha and ,IIRC, ia64 it is 1/1024s. On all other architectures it is
> 1/100s.
> I am working with computers for 25 years now. I know
> the "ticks" of the DOS timer (18 Hz), but I don't expect the Linux "ticks"
> to be the same (because Linux is a 100% different source,
> and because I think that no intelligent brain will use such a
> big time unit in a multitasking system).
> I do this with intention: *you* as an old-fashioned linux
> programmer - and many other here on the net - is knowing
> very well what a "jiffie" is.
1/HZ of a second. Where HZ is a preprocessor constant dependant on platform,
cpu and other stuff
> Shure, I could "do my homework" and find out t
On Wednesday, 13. June 2001 23:12, Pete Zaitcev wrote:
> > From: Wolfgang Mües <[EMAIL PROTECTED]>
> > Can you explain "timeout is in jiffies" to a user who don't know
> > anything about "jiffies" and "ticks" ?
>
> Wolfgang is trying his best to be difficult, so I am not
> replying to his trollin
Pete Zaitcev wrote:
>
> > > > > timeout is in jiffies, and is the time waited from URB submission to
> > > > > getting a -ETIMEOUT if things go wrong. Normally HZ is a good thing to
> > > > > put in here.
>
> Wolfgang is trying his best to be difficult, so I am not
> replying to his trolling. Al
> From: Wolfgang Mües <[EMAIL PROTECTED]>
> Date: Wed, 13 Jun 2001 22:20:09 +0200
> > > > timeout is in jiffies, and is the time waited from URB submission to
> > > > getting a -ETIMEOUT if things go wrong. Normally HZ is a good thing to
> > > > put in here.
> > >
> > > May I ask for the definiti
On Tuesday, 12. June 2001 18:48, Dmitri wrote:
> Quoting Wolfgang Mües <[EMAIL PROTECTED]>:
> > On Monday, 11. June 2001 23:24, Brad Hards wrote:
> > > timeout is in jiffies, and is the time waited from URB submission to
> > > getting a -ETIMEOUT if things go wrong. Normally HZ is a good thing to
Quoting Wolfgang Mües <[EMAIL PROTECTED]>:
> On Monday, 11. June 2001 23:24, Brad Hards wrote:
>
> > timeout is in jiffies, and is the time waited from URB submission to
> > getting a -ETIMEOUT if things go wrong. Normally HZ is a good thing to put
> > in here.
>
> May I ask for the definition
On Monday, 11. June 2001 23:24, Brad Hards wrote:
> timeout is in jiffies, and is the time waited from URB submission to
> getting a -ETIMEOUT if things go wrong. Normally HZ is a good thing to put
> in here.
May I ask for the definition of "jiffies", because I have found nothing
similar in my p
> > And like Georg said, be sure to kmalloc() the data area; don't use local
> > stack or global/static data areas for this.
>
> Can anyone explain this a bit further? Specifically, is this driven by PCI
> address issues, or some kind of alignment requirement for the host controller?
> Is it archi
"Dunlap, Randy" wrote:
> You can only transfer "extra" data (other than the request/setup packet) in
> one direction at a time, right? So the data pointer either points to
> outbound data or to an incoming buffer area, depending on the request,
> which you already know about for your device.
Jus
For the record, I think it's wrong to think of these as the "old"
API, or just "compatibility wrappers" ... they're perfectly fine
synchronous APIs, for the only two cases (control/bulk) where
such APIs make sense.
Also I happen to have noticed that Documentation/usb/ohci.txt
mentions bits and pi
> From: Brad Hards [mailto:[EMAIL PROTECTED]]
>
> "Jerram, Simon" wrote:
>
> > I'm not asking how my device behaves, I wouldn't expect anyone here
> > to know that! I'm just asking a fairly basic question on how to
> > use the USB subsystem. Perhaps it's so basic that people
> > thought it ben
"Jerram, Simon" wrote:
> I'm not asking how my device behaves, I wouldn't expect anyone here
> to know that! I'm just asking a fairly basic question on how to
> use the USB subsystem. Perhaps it's so basic that people
> thought it beneath them to document it. ("Oh it should be obvious
> by loo
Eric HENRY <[EMAIL PROTECTED]>
> usb_control_message gives you only the faculty to send a control messsage
to
> your device as it is described in the USB specs.
Er. Yes I know that. How do I use usb_control_message to send & recieve
messages
as defined in the USB spec. I know how the messages
Title: RE: [linux-usb-devel] Old USB API
Hi Simon,
usb_control_message gives you only the faculty to send a control messsage to your device as it is described in the USB specs. So read usb specs v1.1 chapter 9 for more details.
I think you haven't studied your device enough...
Try to
On Fri, Jun 08, 2001 at 03:34:39PM +0100, Jerram, Simon wrote:
> Is there a decent specification available for this? If not...
>
> The Documentation for the URB API referrs to usb_control_msg
> as being a converter for the old API, and that it is a good
> exapmle on how to use the URB one. To
Is there a decent specification available for this? If not...
The Documentation for the URB API referrs to usb_control_msg
as being a converter for the old API, and that it is a good
exapmle on how to use the URB one. To an extent it is,
but simply looking at it without any documentation on h
21 matches
Mail list logo
