[1.] Problems with ServerWorks OSB4/CSB5 OHCI USB Controller of Dell
PowerEdge 1600SC
[2.] Full description of the problem/report:
Having installed and configured an USRobotics 8500 and a ZyXEL 640-31
ADSL USB Modems with eciadsl-0.9-1 [1] on a Dell PowerEdge 1600SC
running Debian with several cus
On Wed, 15 Sep 2004, Nishanth Aravamudan wrote:
> > Why not simply use wait_event_interruptible()?
>
> I'm not too familiar with the USB code, so I'm not sure if such a change
> is possible in all cases. It may help if I give an example of what I was
> referring to:
>
> drivers/usb/misc/auerswal
> > Why not simply use wait_event_interruptible()?
Good idea. Unfortunately, we lack wait_event_timeout().
> I'm not too familiar with the USB code, so I'm not sure if such a change
> is possible in all cases. It may help if I give an example of what I was
> referring to:
>
> drivers/usb/misc/
On Wed, Sep 15, 2004 at 05:00:57PM -0400, Alan Stern wrote:
> On Wed, 15 Sep 2004, Greg KH wrote:
>
> > Ah, nevermind. See the lkml thread about __iomem for where I was
> > confused. I'll go fix up the hcd drivers now...
>
> There's nothing to be done for the UHCI driver, right? It uses real I
On Wed, 15 Sep 2004, Greg KH wrote:
> Ah, nevermind. See the lkml thread about __iomem for where I was
> confused. I'll go fix up the hcd drivers now...
There's nothing to be done for the UHCI driver, right? It uses real IO,
not memory-mapped IO (in{bwl} rather than read{bwl}).
Alan Stern
Am Mittwoch, 15. September 2004 19:34 schrieb Nishanth Aravamudan:
> Oliver,
>
> It was recommended to me to ask you a question about the proper ordering
> of add_wait_queue() and set_current_state().
>
> In some drivers the order is
>
> set_current_state(TASK_INTERRUPTIBLE);
> add_wait_queue(..
On Wed, Sep 15, 2004 at 03:40:36PM -0400, Alan Stern wrote:
> On Wed, 15 Sep 2004, Nishanth Aravamudan wrote:
>
> > Oliver,
> >
> > It was recommended to me to ask you a question about the proper ordering
> > of add_wait_queue() and set_current_state().
> >
> > In some drivers the order is
> >
On Wed, Sep 15, 2004 at 01:11:03PM -0700, Greg KH wrote:
> On Wed, Sep 15, 2004 at 01:07:55PM -0700, Greg KH wrote:
> > On Wed, Sep 15, 2004 at 11:56:24AM -0700, Greg KH wrote:
> > > Hi,
> > >
> > > I've just applied the patch below to try to clean up the USB host
> > > controller driver warnings
On Wed, Sep 15, 2004 at 01:07:55PM -0700, Greg KH wrote:
> On Wed, Sep 15, 2004 at 11:56:24AM -0700, Greg KH wrote:
> > Hi,
> >
> > I've just applied the patch below to try to clean up the USB host
> > controller driver warnings that sparse spits out about __iomem usages
> > being incorrect.
> >
On Wed, Sep 15, 2004 at 11:56:24AM -0700, Greg KH wrote:
> Hi,
>
> I've just applied the patch below to try to clean up the USB host
> controller driver warnings that sparse spits out about __iomem usages
> being incorrect.
>
> However it looks like you all are just taking a memory section that w
On Wed, 15 Sep 2004, Nishanth Aravamudan wrote:
> Oliver,
>
> It was recommended to me to ask you a question about the proper ordering
> of add_wait_queue() and set_current_state().
>
> In some drivers the order is
>
> set_current_state(TASK_INTERRUPTIBLE);
> add_wait_queue(...);
>
> and in ot
Hi,
I've just applied the patch below to try to clean up the USB host
controller driver warnings that sparse spits out about __iomem usages
being incorrect.
However it looks like you all are just taking a memory section that was
allocated in ioremap() and using that to get values to call readX()
On Wed, 15 Sep 2004, David Brownell wrote:
> > But what should happen to the root hub? It shouldn't be disconnected,
> > because the HCD will try to deregister it later on.
>
> Root hub disconnect is all special cased anyway ... it
> could be done so that's not an issue. There's no parent
>
Oliver,
It was recommended to me to ask you a question about the proper ordering
of add_wait_queue() and set_current_state().
In some drivers the order is
set_current_state(TASK_INTERRUPTIBLE);
add_wait_queue(...);
and in others it is
add_wait_queue(...);
set_current_state(TASK_INTERRUPTIBLE);
On Wed, 15 Sep 2004, Nigel Metheringham wrote:
> For a long time now I have had real problems with USB bulk transfer
> stuff (anything that moves reasonable amounts of data to mass storage
> devices and gnomad2 - an interface to a Creative Zen mp3 player, not
> using a mass storage interface - has
On Wed, 2004-09-15 at 17:40, Pantelis Antoniou wrote:
> Hi all
>
Hi Pantelis, although you're obviously greek, I'll speak in english so
that anybody can understand our conversation...
> I'm in the process of migrating a 2.4 host controller driver
> to 2.6. FYI it's the m8xx host driver.
>
> The
On Wed, 15 Sep 2004 [EMAIL PROTECTED] wrote:
> This is a description of each file attached to this post:
> lspci.log lspci output, to give information on the USB controllers
> that I use.
> uhci-*.logMultiple copy of the content of /proc/driver/uhci/my
Lothar, I'm not going to merge this particular patch
(but the others are already merged):
On Tuesday 07 September 2004 2:18 pm, Lothar Wassmann wrote:
>
>
> The patch below makes sure that ed->tick has been set to the current
> frame number BEFORE enabling the SF interrupt. Otherwise the interr
On Tuesday 14 September 2004 8:10 am, Alan Stern wrote:
> On Mon, 13 Sep 2004, David Brownell wrote:
>
> > The IRQ handler can't do much at all; it just got an IRQ that
> > said the HC died. Resetting the controller is about all it can
> > do (so it's in a known and "safe" state), other than noti
On Wednesday 15 September 2004 8:21 am, Christoph Torens wrote:
> But then I noticed that with the following DEBUG module parameters
> everything works perfectly (the first three parameters are standard).
>
> options hc_isp116x hcport=0xf400 hcport2=0xf402 irq=25
> hc_verbose=1 hc_error
For a long time now I have had real problems with USB bulk transfer
stuff (anything that moves reasonable amounts of data to mass storage
devices and gnomad2 - an interface to a Creative Zen mp3 player, not
using a mass storage interface - has never worked right for me).
Finally a comment on a mai
I noticed some corrections have been made to usb-skeleton.c since version
0.7 which is in the 2.4.22 kernel. However, the most recent version, 1.1,
apparently needs 2.5.?? or higher due to some changes in the structs, etc.
Which version of usb-skeleton.c is the most corrected one that will compil
Hello List,
I've been following all the discussions about the isp116x chip.
I have also some problems with the this chip and postet them to this
list some time ago, but I experienced something new recently.
I am (also) using the Arcom Viper (PXA255) and my task is to get a
bluetooth dongle working.
On Wed, 15 Sep 2004 04:46:30 -0700 (PDT) sunil saggar wrote:
| We (a group of three) are developing device driver for
| usb pen drive in linux environment as my minor project
| in B.tech n facing lot of probs.can u give us
| the source code of device driver for pen drive.i
| have tried
On Wed, 15 Sep 2004, Pantelis Antoniou wrote:
> Hi all
>
> I'm in the process of migrating a 2.4 host controller driver
> to 2.6. FYI it's the m8xx host driver.
>
> The driver in question does not compile now, but works
> OK in the latest 2.4 kernels (2.4.26).
>
> Do you have any pointers for w
Hi all
I'm in the process of migrating a 2.4 host controller driver
to 2.6. FYI it's the m8xx host driver.
The driver in question does not compile now, but works
OK in the latest 2.4 kernels (2.4.26).
Do you have any pointers for what I'll have to take care
during porting?
Regards
Pantelis
On Wed, 15 Sep 2004, sunil saggar wrote:
> We (a group of three) are developing device driver for
> usb pen drive in linux environment as my minor project
> in B.tech n facing lot of probs.can u give us
> the source code of device driver for pen drive.i
> have tried looking for that in
On Tue, 14 Sep 2004, Andrew Morton wrote:
> Someone tried to create an already-existing slab cache.
Judging from the stack trace, it looks like the guilty party lies in the
SCSI subsystem. This bug should be reassigned to them.
> Begin forwarded message:
>
> Date: Tue, 14 Sep 2004 21:53:22 -0
On Wednesday 15 September 2004 12:42 am, Guilhem Lavaux wrote:
> Hi,
>
> Here is a patch against linux-2.6.8.1 to make usbnet works with freebox.
> This device is an ADSL modem which does not return a valid MAC
> address. CDCEther was working with it in linux-2.4 because it was not
> checking
Hello Luc,
On Tue, 14 Sep 2004 17:39:18 +0200 Luc Saillard <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I've made a patch to (re)add pwc philips driver into the kernel. This driver
> have support for some compression mode (for chipset 2 & 3), so you don't
> need the binary module to grab an image in [
We (a group of three) are developing device driver for
usb pen drive in linux environment as my minor project
in B.tech n facing lot of probs.can u give us
the source code of device driver for pen drive.i
have tried looking for that in linux kernel source as
well but that was not easy t
On Wednesday 15 Sep 2004 20:48, Stelian Pop wrote:
> On Tue, Sep 14, 2004 at 05:39:18PM +0200, Luc Saillard wrote:
> > The patch is 300kbytes long, i don't include it in this mail. You can
> > found a tarball or a patch against the last linux kernel at:
> >
> > http://www.saillard.org/pwc/lin
On Mon, 2004-09-13 at 22:51, Lothar Wassmann wrote:
> The PXA processor doesn't have something like I/O address space.
> As far as I understand your device is a real PCI device. So you
> probably wouldn't use a platform_device as base, but a pci_dev.
> You should have a look at drivers/usb/core/hcd
Duncan Sands wrote:
Here is a patch against linux-2.6.8.1 to make usbnet works with freebox.
This device is an ADSL modem which does not return a valid MAC
address. CDCEther was working with it in linux-2.4 because it was not
checking the MAC address.
Hi Guilhem, it does have a MAC address, bu
On Tue, Sep 14, 2004 at 05:39:18PM +0200, Luc Saillard wrote:
> Hi,
>
> I've made a patch to (re)add pwc philips driver into the kernel. This driver
> have support for some compression mode (for chipset 2 & 3), so you don't
> need the binary module to grab an image in [EMAIL PROTECTED]
[...]
>
> Here is a patch against linux-2.6.8.1 to make usbnet works with freebox.
> This device is an ADSL modem which does not return a valid MAC
> address. CDCEther was working with it in linux-2.4 because it was not
> checking the MAC address.
Hi Guilhem, it does have a MAC address, but there are
Hi,
On Tue, 14 Sep 2004, Lothar Wassmann wrote:
> I would like to keep the code as general as possible, so everything
> what's platform or chip dependent should be clearly separated from the
> generic stuff. For this it will be very helpful to see what has to be
> done different on different hard
Hi,
Here is a patch against linux-2.6.8.1 to make usbnet works with freebox.
This device is an ADSL modem which does not return a valid MAC
address. CDCEther was working with it in linux-2.4 because it was not
checking the MAC address.
Regards,
Guilhem Lavaux.
diff -ur -x '*.o' -x '.*.cmd' -x
38 matches
Mail list logo
