Hi, All:
I noticed a small problem today. If I pull a _power_ cable
on my hub, it becomes disabled with the following message:
hub.c: error resetting hub 3 - disconnecting
It comes back to life if I pull and reinsert its upstream USB
cable (also may trigger an unrelated khubd lockup that I disc
Hello:
I am having some misunderstanding with the list software,
so I am sending this backwards, with To: list, cc: Johannes
I found that my fix for interlock between disconnects and khubd
was not entirely correct. The khubd can call usb_hub_disconnect,
which disconnects the hub under processing
> The main problem with the data memory is simply that some locations are not
> guaranteed to map continuosly to PCI space, so that accidently crossing a
> page boundary may fail.
That sounds like an issue that pci_map_single() and siblings should
be addressing ... but the last time I checked, on
> From: David Brownell [mailto:[EMAIL PROTECTED]]
> > Instead of making another USB-specific file system, why
> don't you try to make
> > a generic device tree for all busses?
>
> That was one of the options I was alluding to when I said
> "less evolutionary". Getting rid of "usbdevfs" might
On Wed, Apr 11, 2001 at 11:28:33PM +0200, Martin Diehl wrote:
<...>
> My concern on alignment is based on:
>
> PCI is 32 bit wide (at least) and BM-DMA is probably done using
> burst-cycles, i.e. 32 bit transfered for every PCI clock and _no_ address
> line incrementing by the BM-device (the BM-
Is this patch necessary? That is, is the behavior incorrect without the
patch?
Matt Dharm
On Thu, Apr 12, 2001 at 04:42:17AM -0700, Wim Coekaerts wrote:
> This adds the new models of the iomega zip 100 and 250 to usb-storage. (tested)
>
> --- linux-2.2.19/drivers/usb/usb-storage.cWed Apr 1
My most recent note from AMD said that they'd be sending
the workaround information to LKML and David Brownell
today. I'll send a quick query and see if they are on track
to still do this. A couple of days ago the documentation was
still going through their internal review process.
Mile
If AMD doesn't publish their workaround soon, I'd be inclined
to send a patch like this to Linus. The "WILL KILL SYSTEM"
bit is overstated ... it's not quite that certain.
- Original Message -
From: "Manuel Estrada Sainz" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, April
> From: "Tim Jansen" <[EMAIL PROTECTED]>
> Sent: Wednesday, April 11, 2001 2:04 PM
> Subject: Re: [linux-usb-devel] Hotplugging and locks?
>
> On Wednesday 11 April 2001 20:04, you wrote:
> > > When the device is disconnected in usb_disconnect() the usb_device struct
> > > is freed, but no one pre
On Wednesday 11 April 2001 23:10, you wrote:
> We use reference counting for most of the structures we use. The ioctl
> (or usbdevfs) should increment the reference count on the device when
> the application open's the device.
> When usb_disconnect gets called, it'll decrement the reference count
Hello all,
I personaly didn't have much trouble with my AMD-756 and anyway, I
can't exchange the hardware so I wrote the following patch agains 2.4.3
to be able to force usage of my hardware.
I tried to clearly state that doing so is dangerous, if someone finds
a more frightening way of sa
Sorry, I forgot to attach the saa7111-new.c.
Here it is.
> a) 0x08 subaddress with value 0x08 is causing the black & white display.
> if I change this value back to the original value of 0xc8 then the colour
> comes back.
OK. That's no problem to me. Bit 7 enables the automatic fiel
When we have a look into the saa7111a datasheet (chapter 17), we will find
some registers that may effect the color:
- Chrominance control: Subaddress 0x0E old value 0x01, new value 0x01
- GUDL:Subaddress 0x02 old value 0xD0, new value 0xC0
- BYPS:Subaddress 0
Hi Dwaine,
Most of the parameters of the old setting are ok for me. But HSB and HSS
at subaddress 0x06 and 0x07
in the saa7111a don't match for PAL - the data stream often hangs. I
have modified the saa7111-new.c in that way, that you can adjust HSB by
tuning HUE and HSS by tuning the color satur
This adds the new models of the iomega zip 100 and 250 to usb-storage. (tested)
--- linux-2.2.19/drivers/usb/usb-storage.c Wed Apr 11 19:59:30 2001
+++ linux-2.2.19p1/drivers/usb/usb-storage.cWed Apr 11 19:53:59 2001
@@ -1640,6 +1640,12 @@
"Y-E Data Flashbuster-U", US_SC_UFI, U
G'day
I was playing around with some testing of a new UPS (HID power class). I
hit any
Oops on boot (had a hub and the UPS plugged in) - kernel bug in slab.c
line 1097,
which is
if (flags & ~(SLAB_DMA|SLAB_LEVEL_MASK|SLAB_NO_GROW))
BUG();
I have 2.4.3, with ac4 patch an
16 matches
Mail list logo
