Hello,
On Thu, May 10, 2007 03:38, Jeff Garzik wrote:
This was ACK'd by Greg, as you see in the sign-offs. See the commit
below for rationale.
USB is now treated like other buses, for network drivers:
* USB network driver patches should go to me and netdev
* Just like in PCI or PCMCIA
On Thursday 10 May 2007 14:12:47 Indan Zupancic wrote:
Hello,
On Thu, May 10, 2007 03:38, Jeff Garzik wrote:
This was ACK'd by Greg, as you see in the sign-offs. See the commit
below for rationale.
USB is now treated like other buses, for network drivers:
* USB network driver
On Tue, 2007-05-08 at 10:30 -0700, Pete Zaitcev wrote:
On Tue, 08 May 2007 08:48:26 +0200, Paolo Abeni [EMAIL PROTECTED] wrote:
That will be a better solution, but most unfortunately it does not fit
easily with libpcap design: libpcap is designed to provide a whole frame
in a contiguous
devt_attr and uevent_attr are either allocated dynamically with or
embedded in device and class_device as they needed their owner field
set to the module implementing the driver. Now that sysfs implements
immediate disconnect and owner field removed from struct attribute,
there is no reason to do
Currently, devt_attr for the dev file is freed immediately on device
removal, but if the dev sysfs file is open when a device is removed,
sysfs will access its attribute structure for further access including
close resulting in jumping to garbled address. Fix it by postponing
freeing devt_attr to
On Thu, May 10, 2007 at 04:45:17PM +0200, Tejun Heo wrote:
Currently, devt_attr for the dev file is freed immediately on device
removal, but if the dev sysfs file is open when a device is removed,
sysfs will access its attribute structure for further access including
close resulting in jumping
Greg KH wrote:
Applies well to 2.6.20 and 21. As sysfs-immediate-disconnect doesn't
seem to be included in 2.6.22, this should be included in linus#master
too (applies well there as well).
As I don't think we should be adding your sysfs rework to 2.6.22 just
yet, any objections to me just
On Wed, 9 May 2007, Stanislaw Gruszka wrote:
Can you please provide the dmesg log from the Pentium-2 machine with UHCI
and with CONFIG_USB_DEBUG set? Show what happens when you connect the
mouse and then plug in the ueagle-atm device.
Ok, in dmesk.2 the modem is connected when there is
On 5/10/07, Tejun Heo [EMAIL PROTECTED] wrote:
Currently, devt_attr for the dev file is freed immediately on device
removal, but if the dev sysfs file is open when a device is removed,
sysfs will access its attribute structure for further access including
close resulting in jumping to garbled
On Thu, May 10, 2007 at 05:13:10PM +0200, Tejun Heo wrote:
Greg KH wrote:
Applies well to 2.6.20 and 21. As sysfs-immediate-disconnect doesn't
seem to be included in 2.6.22, this should be included in linus#master
too (applies well there as well).
As I don't think we should be adding
Kay Sievers wrote:
On 5/10/07, Tejun Heo [EMAIL PROTECTED] wrote:
Currently, devt_attr for the dev file is freed immediately on device
removal, but if the dev sysfs file is open when a device is removed,
sysfs will access its attribute structure for further access including
close resulting in
On Thu, 10 May 2007, Tejun Heo wrote:
Currently, devt_attr for the dev file is freed immediately on device
removal, but if the dev sysfs file is open when a device is removed,
sysfs will access its attribute structure for further access including
close resulting in jumping to garbled address.
Hi Jeff,
On May 9 2007 21:38, Jeff Garzik wrote:
diff --git a/drivers/net/Makefile b/drivers/net/Makefile
index 59c0459..c5d8423 100644
--- a/drivers/net/Makefile
+++ b/drivers/net/Makefile
@@ -206,6 +206,14 @@ obj-$(CONFIG_TR) += tokenring/
obj-$(CONFIG_WAN) += wan/
obj-$(CONFIG_ARCNET) +=
Alan Stern wrote:
On Thu, 10 May 2007, Tejun Heo wrote:
Currently, devt_attr for the dev file is freed immediately on device
removal, but if the dev sysfs file is open when a device is removed,
sysfs will access its attribute structure for further access including
close resulting in jumping
On Wednesday 09 May 2007, David Brownell wrote:
On Wednesday 09 May 2007, Laurent Pinchart wrote:
Could you elaborate a bit on the subject ? Which allocator calls should I
use ? Just kmalloc ? When does a USB driver need cache coherent buffers ?
Using kmalloc() should be fine.
The
This patch (as904) adds code to check for endpoint descriptor bInterval
values outside the legal limits. Illegal values are set to 32 ms, which
seems like a reasonable default.
This fixes Bugzilla #8432.
Signed-off-by: Alan Stern [EMAIL PROTECTED]
---
Index: usb-2.6/drivers/usb/core/config.c
Greg:
You have applied most of the patches I sent, but not the USB-persist
ones. Any particular reason?
The infrastructure added for USB-persist is also used for a new type of
quirks entry (devices which need to be reset when they resume). Would you
prefer it if I separate out that common
ÃçÃÃÃèê·¢*ñÃëêõ£º£¨0£©£±£³£¶-£±£²£¹£µ-£³£³£¸£µ
ÃêÃéÃëµÃýÃÃÃÃÃøÃ᣼http://www.fapiao.oen.cn/
http://szhm89.b2b.hc360.com/
н¨ Îı¾Îĵµ.txt
Description: Binary data
Hello,
I'm writing a gadget driver runing on a TI Davinci ARM using the musb_hdrc
controller driver (peripheral mode) and have run into the following:
I'm writing 600k of data via bulk ep IN to host, breaking it up into
32k blocks per ep_request - PIO mode (although same occurs when using DMA)
---
Èç ²» Ðè Òª Ïà ¹Ø ÐŠϢ Çë »Ø ¸´ ÍË ¶¨ ÓÊ [EMAIL PROTECTED]
---
¸Ú λ ·Ö Îö¡¢ÈÎ Ö° ×Ê ¸ñ Óë н ³ê Éè ¼Æ
On Fri, May 04, 2007 at 11:56:18AM -0400, Alan Stern wrote:
From: Danny Budik [EMAIL PROTECTED]
This patch (as899) adds a new ioctl to usbfs: USBDEVFS_GETFRAMENUM.
It allows user programs to obtain the current Start-Of-Frame number on
a USB bus.
Note that the values returned by the
On Thu, May 10, 2007 at 02:10:07PM -0400, Alan Stern wrote:
Greg:
You have applied most of the patches I sent, but not the USB-persist
ones. Any particular reason?
The main reason is that I'm still on the road, and I really want to
spend the time and test those patches, as I'm still not
Dear Yahoo! Groups member,
You belong to one or more email groups provided by Yahoo! Groups
(groups.yahoo.com).
Recently, messages sent to you from Yahoo! Groups have been
returned to us as undeliverable. As a result, we have temporarily
turned off message delivery to this email address.
If
ÃçÃÃÃèê·¢*ñÃëêõ£º£¨0£©£±£³£¶-£±£²£¹£µ-£³£³£¸£µ
ÃêÃéÃëµÃýÃÃÃÃÃøÃ᣼http://www.fapiao.oen.cn/
http://szhm89.b2b.hc360.com/
н¨ Îı¾Îĵµ.txt
Description: Binary data
24 matches
Mail list logo
