Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.

Dismiss

freebsd-usb Digest, Vol 283, Issue 2

5 views

Skip to first unread message

freebsd-u...@freebsd.org

unread,

Apr 9, 2010, 10:54:48 AM4/9/10

to freeb...@freebsd.org

Send freebsd-usb mailing list submissions to
freeb...@freebsd.org

To subscribe or unsubscribe via the World Wide Web, visit
http://lists.freebsd.org/mailman/listinfo/freebsd-usb
or, via email, send a message with subject or body 'help' to
freebsd-u...@freebsd.org

You can reach the person managing the list at
freebsd-...@freebsd.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of freebsd-usb digest..."

Today's Topics:

1. Re: 7.3: instant panic upon connecting a umass (Julian H. Stacey)
2. usb/145455: USB debug support cannot be disabled (Sebastian Huber)
3. Re: 7.3: instant panic upon connecting a umass
(Giovanni Trematerra)
4. Re: usb/145455: USB debug support cannot be disabled
(Hans Petter Selasky)
5. Re: usb/145455: USB debug support cannot be disabled
(Hans Petter Selasky)
6. Re: usb/145455: USB debug support cannot be disabled
(Sebastian Huber)
7. Re: usb touch screen support? (Vulpes Velox)
8. Syncronous Interrupt Transfer (Chris Telting)
9. Re: WIP: usb touchscreen drivers (Zane C.B.)
10. Re: Syncronous Interrupt Transfer (Hans Petter Selasky)
11. Re: 7.3: instant panic upon connecting a umass (Andriy Gapon)
12. Re: 7.3: instant panic upon connecting a umass (Julian H. Stacey)
13. usb/145484: mxxglgxt (mxxglgxt)
14. Re: usb/145484: mxxglgxt (h...@FreeBSD.org)
15. usb/145493: cywyynou (cywyynou)
16. usb/145506: fkucedic (fkucedic)
17. Re: usb/145493: cywyynou (h...@FreeBSD.org)
18. Re: usb/145506: fkucedic (h...@FreeBSD.org)
19. usb/145513: New USB stack: no new devices after forced usb
flash detach (Krutov Mikle)
20. Re: usb/145513: New USB stack: no new devices after forced
usb flash detach (Hans Petter Selasky)
21. Re: usb/145513: New USB stack: no new devices after forced
usb flash detach (Hans Petter Selasky)
22. Re: usb/145513: New USB stack: no new devices after forced
usb flash detach (Hans Petter Selasky)
23. Re: usb/145513: New USB stack: no new devices after forced
usb flash detach (Hans Petter Selasky)
24. Re: usb/145513: New USB stack: no new devices after forced
usb flash detach (Mikle Krutov)
25. Re: usb/145513: New USB stack: no new devices after forced
usb flash detach (Mikle Krutov)
26. usb/145540: yzhxfsnj (yzhxfsnj)
27. usb/145544: jqwgjvle (jqwgjvle)
28. usb/145545: ubnbamwa (ubnbamwa)
29. Re: usb/145540: yzhxfsnj (h...@FreeBSD.org)
30. Re: usb/145544: jqwgjvle (h...@FreeBSD.org)
31. Re: usb/145545: ubnbamwa (h...@FreeBSD.org)
32. Re: usb/145527: Re: usb/141313: [usb8] nvidia USB 2.0
controller - stops copying on USB (lin...@FreeBSD.org)
33. Re: usb/141313: [usb8] nvidia USB 2.0 controller - stops
copying on USB [regression] (tho...@FreeBSD.org)
34. Re: usb/145237: [usbdevs] [patch] Add support for Matrix
Orbital MOU display (Nick Hibma)
35. USB Keyboard puzzle (Rohit Grover)

----------------------------------------------------------------------

Message: 1
Date: Wed, 07 Apr 2010 13:20:17 +0200
From: "Julian H. Stacey" <j...@berklix.com>
Subject: Re: 7.3: instant panic upon connecting a umass
To: "Mikhail T." <mi+...@aldan.algebra.com>
Cc: u...@freebsd.org, sta...@freebsd.org, Jeremy Chadwick
<fre...@jdc.parodius.com>
Message-ID: <201004071120....@fire.js.berklix.net>

Hi,
Reference:
> From: "Mikhail T." <mi+...@aldan.algebra.com>
> Date: Wed, 07 Apr 2010 00:26:46 -0400
> Message-id: <4BBC0986...@aldan.algebra.com>

"Mikhail T." wrote:
> Jeremy Chadwick написав(ла):
> > Regarding your problem: it likely has nothing to do with SMP, so don't
> > worry about that aspect of it.
> Thanks for the reassuring response, Jeremy. If this is not about SMP,
> then there is a (bad) regression -- the 7.2-kernel from March 5 never
> crashed this way... I connected the same phone numerous times, as well
> as the camera...

I wonder if it's eg a corrupt FS not being fsck'd first ? Did you
try patching out your devd.conf entry, & running by hand each stage
of whatever is listed in there for that USB device ?

Cheers,
Julian
--
Julian Stacey: BSD Unix Linux C Sys Eng Consultants Munich http://berklix.com
Mail plain text, Not HTML quoted-printable Base64 http://www.asciiribbon.org

------------------------------

Message: 2
Date: Wed, 7 Apr 2010 12:49:43 GMT
From: Sebastian Huber <sebasti...@embedded-brains.de>
Subject: usb/145455: USB debug support cannot be disabled
To: freebsd-gn...@FreeBSD.org
Message-ID: <201004071249....@www.freebsd.org>

>Number: 145455
>Category: usb
>Synopsis: USB debug support cannot be disabled
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: freebsd-usb
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Wed Apr 07 12:50:05 UTC 2010
>Closed-Date:
>Last-Modified:
>Originator: Sebastian Huber
>Release: 9-current
>Organization:
embedded brains GmbH
>Environment:
>Description:
You cannot disable the USB debug support completely (USB_DEBUG define) due to an intermix of #if and #ifdef handling. The header file usb_freebsd.h defines USB_DEBUG if it is undefined. So the USB_DEBUG pre-processor symbol is always defined. Thus you cannot use #ifdef and #ifndef to test if debugging support should be enabled or disabled.
>How-To-Repeat:

>Fix:
Please have a look at the attached patch.

Patch attached with submission follows:

Index: dev/usb/controller/at91dci.c
===================================================================
--- dev/usb/controller/at91dci.c (revision 206339)
+++ dev/usb/controller/at91dci.c (working copy)
@@ -89,7 +89,7 @@
#define AT9100_DCI_PC2SC(pc) \
AT9100_DCI_BUS2SC(USB_DMATAG_TO_XROOT((pc)->tag_parent)->bus)

-#ifdef USB_DEBUG
+#if USB_DEBUG
static int at91dcidebug = 0;

SYSCTL_NODE(_hw_usb, OID_AUTO, at91dci, CTLFLAG_RW, 0, "USB at91dci");
Index: dev/usb/controller/atmegadci.c
===================================================================
--- dev/usb/controller/atmegadci.c (revision 206339)
+++ dev/usb/controller/atmegadci.c (working copy)
@@ -81,7 +81,7 @@
#define ATMEGA_PC2SC(pc) \
ATMEGA_BUS2SC(USB_DMATAG_TO_XROOT((pc)->tag_parent)->bus)

-#ifdef USB_DEBUG
+#if USB_DEBUG
static int atmegadci_debug = 0;

SYSCTL_NODE(_hw_usb, OID_AUTO, atmegadci, CTLFLAG_RW, 0, "USB ATMEGA DCI");
Index: dev/usb/controller/musb_otg.c
===================================================================
--- dev/usb/controller/musb_otg.c (revision 206339)
+++ dev/usb/controller/musb_otg.c (working copy)
@@ -83,7 +83,7 @@
#define MUSBOTG_PC2SC(pc) \
MUSBOTG_BUS2SC(USB_DMATAG_TO_XROOT((pc)->tag_parent)->bus)

-#ifdef USB_DEBUG
+#if USB_DEBUG
static int musbotgdebug = 0;

SYSCTL_NODE(_hw_usb, OID_AUTO, musbotg, CTLFLAG_RW, 0, "USB musbotg");
Index: dev/usb/controller/uhci_pci.c
===================================================================
--- dev/usb/controller/uhci_pci.c (revision 206339)
+++ dev/usb/controller/uhci_pci.c (working copy)
@@ -372,7 +372,7 @@
* that the BIOS won't touch the keyboard anymore if it is connected
* to the ports of the root hub?
*/
-#ifdef USB_DEBUG
+#if USB_DEBUG
if (pci_read_config(self, PCI_LEGSUP, 2) != PCI_LEGSUP_USBPIRQDEN) {
device_printf(self, "LegSup = 0x%04x\n",
pci_read_config(self, PCI_LEGSUP, 2));
Index: dev/usb/controller/usb_controller.c
===================================================================
--- dev/usb/controller/usb_controller.c (revision 206339)
+++ dev/usb/controller/usb_controller.c (working copy)
@@ -72,7 +72,7 @@

/* static variables */

-#ifdef USB_DEBUG
+#if USB_DEBUG
static int usb_ctrl_debug = 0;

SYSCTL_NODE(_hw_usb, OID_AUTO, ctrl, CTLFLAG_RW, 0, "USB controller");
Index: dev/usb/controller/avr32dci.c
===================================================================
--- dev/usb/controller/avr32dci.c (revision 206339)
+++ dev/usb/controller/avr32dci.c (working copy)
@@ -81,7 +81,7 @@
#define AVR32_PC2SC(pc) \
AVR32_BUS2SC(USB_DMATAG_TO_XROOT((pc)->tag_parent)->bus)

-#ifdef USB_DEBUG
+#if USB_DEBUG
static int avr32dci_debug = 0;

SYSCTL_NODE(_hw_usb, OID_AUTO, avr32dci, CTLFLAG_RW, 0, "USB AVR32 DCI");
Index: dev/usb/controller/ohci.c
===================================================================
--- dev/usb/controller/ohci.c (revision 206339)
+++ dev/usb/controller/ohci.c (working copy)
@@ -78,7 +78,7 @@
((ohci_softc_t *)(((uint8_t *)(bus)) - \
((uint8_t *)&(((ohci_softc_t *)0)->sc_bus))))

-#ifdef USB_DEBUG
+#if USB_DEBUG
static int ohcidebug = 0;

SYSCTL_NODE(_hw_usb, OID_AUTO, ohci, CTLFLAG_RW, 0, "USB ohci");
@@ -228,7 +228,7 @@
device_printf(sc->sc_bus.bdev, "reset timeout\n");
return (USB_ERR_IOERROR);
}
-#ifdef USB_DEBUG
+#if USB_DEBUG
if (ohcidebug > 15) {
ohci_dumpregs(sc);
}
@@ -287,7 +287,7 @@
sc->sc_noport = OHCI_GET_NDP(OREAD4(sc, OHCI_RH_DESCRIPTOR_A));
}

-#ifdef USB_DEBUG
+#if USB_DEBUG
if (ohcidebug > 5) {
ohci_dumpregs(sc);
}
@@ -403,7 +403,7 @@

usb_callout_init_mtx(&sc->sc_tmo_rhsc, &sc->sc_bus.bus_mtx, 0);

-#ifdef USB_DEBUG
+#if USB_DEBUG
if (ohcidebug > 15) {
for (i = 0; i != OHCI_NO_EDS; i++) {
printf("ed#%d ", i);
@@ -456,7 +456,7 @@

USB_BUS_LOCK(&sc->sc_bus);

-#ifdef USB_DEBUG
+#if USB_DEBUG
DPRINTF("\n");
if (ohcidebug > 2) {
ohci_dumpregs(sc);
@@ -486,7 +486,7 @@
{
uint32_t ctl;

-#ifdef USB_DEBUG
+#if USB_DEBUG
DPRINTF("\n");
if (ohcidebug > 2) {
ohci_dumpregs(sc);
@@ -520,7 +520,7 @@
ohci_do_poll(&sc->sc_bus);
}

-#ifdef USB_DEBUG
+#if USB_DEBUG
static void
ohci_dumpregs(ohci_softc_t *sc)
{
@@ -767,7 +767,7 @@
panic("%s:%d: out of TD's\n",
__FUNCTION__, __LINE__);
}
-#ifdef USB_DEBUG
+#if USB_DEBUG
if (ohcidebug > 5) {
DPRINTF("isoc TD\n");
ohci_dump_itd(td);
@@ -808,7 +808,7 @@
ohci_device_done(xfer, USB_ERR_NORMAL_COMPLETION);
}

-#ifdef USB_DEBUG
+#if USB_DEBUG
static const char *const
ohci_cc_strs[] =
{
@@ -936,7 +936,7 @@
DPRINTFN(13, "xfer=%p endpoint=%p transfer done\n",
xfer, xfer->endpoint);

-#ifdef USB_DEBUG
+#if USB_DEBUG
if (ohcidebug > 10) {
ohci_dump_tds(xfer->td_transfer_first);
}
@@ -1161,7 +1161,7 @@

DPRINTFN(16, "real interrupt\n");

-#ifdef USB_DEBUG
+#if USB_DEBUG
if (ohcidebug > 15) {
ohci_dumpregs(sc);
}
@@ -1587,7 +1587,7 @@

xfer->td_transfer_last = td;

-#ifdef USB_DEBUG
+#if USB_DEBUG
if (ohcidebug > 8) {
DPRINTF("nexttog=%d; data before transfer:\n",
xfer->endpoint->toggle_next);
@@ -2018,7 +2018,7 @@

xfer->td_transfer_last = td_last;

-#ifdef USB_DEBUG
+#if USB_DEBUG
if (ohcidebug > 8) {
DPRINTF("data before transfer:\n");
ohci_dump_itds(xfer->td_transfer_first);
Index: dev/usb/usb_debug.h
===================================================================
--- dev/usb/usb_debug.h (revision 206339)
+++ dev/usb/usb_debug.h (working copy)
@@ -34,7 +34,7 @@

/* Check if USB debugging is enabled. */
#ifdef USB_DEBUG_VAR
-#if (USB_DEBUG != 0)
+#if USB_DEBUG
#define DPRINTFN(n,fmt,...) do { \
if ((USB_DEBUG_VAR) >= (n)) { \
printf("%s: " fmt, \
Index: dev/usb/storage/umass.c
===================================================================
--- dev/usb/storage/umass.c (revision 206339)
+++ dev/usb/storage/umass.c (working copy)
@@ -2147,7 +2147,7 @@
static void
umass_cam_attach(struct umass_softc *sc)
{
-#ifndef USB_DEBUG
+#if !USB_DEBUG
if (bootverbose)
#endif
printf("%s:%d:%d:%d: Attached to scbus%d\n",
Index: dev/usb/usb_busdma.c
===================================================================
--- dev/usb/usb_busdma.c (revision 206339)
+++ dev/usb/usb_busdma.c (working copy)
@@ -440,7 +440,7 @@
pc->page_offset_buf = rem;
pc->page_offset_end += rem;
nseg--;
-#ifdef USB_DEBUG
+#if USB_DEBUG
if (rem != (USB_P2U(pc->buffer) & (USB_PAGE_SIZE - 1))) {
/*
* This check verifies that the physical address is correct:
Index: dev/usb/usb_hub.c
===================================================================
--- dev/usb/usb_hub.c (revision 206339)
+++ dev/usb/usb_hub.c (working copy)
@@ -73,7 +73,7 @@
#define UHUB_INTR_INTERVAL 250 /* ms */
#define UHUB_N_TRANSFER 1

-#ifdef USB_DEBUG
+#if USB_DEBUG
static int uhub_debug = 0;

SYSCTL_NODE(_hw_usb, OID_AUTO, uhub, CTLFLAG_RW, 0, "USB HUB");
Index: dev/usb/usb_dev.c
===================================================================
--- dev/usb/usb_dev.c (revision 206339)
+++ dev/usb/usb_dev.c (working copy)
@@ -79,7 +79,7 @@

#if USB_HAVE_UGEN

-#ifdef USB_DEBUG
+#if USB_DEBUG
static int usb_fifo_debug = 0;

SYSCTL_NODE(_hw_usb, OID_AUTO, dev, CTLFLAG_RW, 0, "USB device");
Index: dev/usb/usb_freebsd.h
===================================================================
--- dev/usb/usb_freebsd.h (revision 206339)
+++ dev/usb/usb_freebsd.h (working copy)
@@ -57,7 +57,7 @@
#define USB_HUB_MAX_DEPTH 5
#define USB_EP0_BUFSIZE 1024 /* bytes */

-#ifndef USB_DEBUG
+#if USB_DEBUG
#define USB_DEBUG 1
#endif

Index: dev/usb/net/uhso.c
===================================================================
--- dev/usb/net/uhso.c (revision 206339)
+++ dev/usb/net/uhso.c (working copy)
@@ -280,7 +280,7 @@
SYSCTL_INT(_hw_usb_uhso, OID_AUTO, auto_switch, CTLFLAG_RW,
&uhso_autoswitch, 0, "Automatically switch to modem mode");

-#ifdef USB_DEBUG
+#if USB_DEBUG
#ifdef UHSO_DEBUG
static int uhso_debug = UHSO_DEBUG;
#else
Index: dev/usb/usb_generic.c
===================================================================
--- dev/usb/usb_generic.c (revision 206339)
+++ dev/usb/usb_generic.c (working copy)
@@ -124,7 +124,7 @@
.f_stop_write = &ugen_stop_io,
};

-#ifdef USB_DEBUG
+#if USB_DEBUG
static int ugen_debug = 0;

SYSCTL_NODE(_hw_usb, OID_AUTO, ugen, CTLFLAG_RW, 0, "USB generic");
Index: dev/usb/usb_process.c
===================================================================
--- dev/usb/usb_process.c (revision 206339)
+++ dev/usb/usb_process.c (working copy)
@@ -77,7 +77,7 @@
#define USB_THREAD_EXIT(err) kthread_exit(err)
#endif

-#ifdef USB_DEBUG
+#if USB_DEBUG
static int usb_proc_debug;

SYSCTL_NODE(_hw_usb, OID_AUTO, proc, CTLFLAG_RW, 0, "USB process");

>Release-Note:
>Audit-Trail:
>Unformatted:

------------------------------

Message: 3
Date: Wed, 7 Apr 2010 14:38:20 +0200
From: Giovanni Trematerra <giovanni....@gmail.com>
Subject: Re: 7.3: instant panic upon connecting a umass
To: "Mikhail T." <mi+...@aldan.algebra.com>
Cc: u...@freebsd.org, sta...@freebsd.org, Jeremy Chadwick
<fre...@jdc.parodius.com>
Message-ID:
<h2h4e6cba831004070538w1...@mail.gmail.com>
Content-Type: text/plain; charset=KOI8-R

2010/4/7 Mikhail T. <mi+...@aldan.algebra.com>:
> Jeremy Chadwick написав(ла):
>> Regarding your problem: it likely has nothing to do with SMP, so don't
>> worry about that aspect of it.
> Thanks for the reassuring response, Jeremy. If this is not about SMP,
> then there is a (bad) regression -- the 7.2-kernel from March 5 never
> crashed this way... I connected the same phone numerous times, as well
> as the camera...
>
> I shall await response from USB-maintainers...

While in the meantime why not compile a kernel with -DUSB_DEBUG and
report back the trace before the panic?

If it's not an issue for you, you could try to upgrade to 8.0-RELEASE
that has a completely new usb stack as Jeremy pointed out.

Thanks

--
Gianni

------------------------------

Message: 4
Date: Wed, 7 Apr 2010 16:16:18 +0200
From: Hans Petter Selasky <hsel...@c2i.net>
Subject: Re: usb/145455: USB debug support cannot be disabled
To: freeb...@freebsd.org
Cc: freebsd-gn...@freebsd.org
Message-ID: <201004071616....@c2i.net>
Content-Type: Text/Plain; charset="iso-8859-15"

On Wednesday 07 April 2010 14:49:43 Sebastian Huber wrote:
> 145455
>

Hi,

Your patch looks good and has been committed to USB P4.

The patch to "usb_freebsd.h" was not committed, because we want to force
debugging on by default until further unless you define USB_DEBUG=0 in your
kernel config file.

Please check and verify:

http://p4db.freebsd.org/changeView.cgi?CH=176614&ignore=GO!

--HPS

------------------------------

Message: 5
Date: Wed, 7 Apr 2010 14:20:03 GMT
From: Hans Petter Selasky <hsel...@c2i.net>
Subject: Re: usb/145455: USB debug support cannot be disabled
To: freeb...@FreeBSD.org
Message-ID: <201004071420....@freefall.freebsd.org>

The following reply was made to PR usb/145455; it has been noted by GNATS.

From: Hans Petter Selasky <hsel...@c2i.net>
To: freeb...@freebsd.org
Cc: Sebastian Huber <sebasti...@embedded-brains.de>,
freebsd-gn...@freebsd.org
Subject: Re: usb/145455: USB debug support cannot be disabled
Date: Wed, 7 Apr 2010 16:16:18 +0200

On Wednesday 07 April 2010 14:49:43 Sebastian Huber wrote:
> 145455
>

Hi,

Your patch looks good and has been committed to USB P4.

The patch to "usb_freebsd.h" was not committed, because we want to force
debugging on by default until further unless you define USB_DEBUG=0 in your
kernel config file.

Please check and verify:

http://p4db.freebsd.org/changeView.cgi?CH=176614&ignore=GO!

--HPS

------------------------------

Message: 6
Date: Wed, 07 Apr 2010 16:29:46 +0200
From: Sebastian Huber <sebasti...@embedded-brains.de>
Subject: Re: usb/145455: USB debug support cannot be disabled
To: freeb...@freebsd.org
Message-ID: <4BBC96DA...@embedded-brains.de>
Content-Type: text/plain; charset=ISO-8859-1

Hi,

it looks good. I am sorry that usb_freebsd.h was included in the patch.

Have a nice day!

On 04/07/2010 04:20 PM, Hans Petter Selasky wrote:
> The following reply was made to PR usb/145455; it has been noted by GNATS.
>
> From: Hans Petter Selasky <hsel...@c2i.net>
> To: freeb...@freebsd.org
> Cc: Sebastian Huber <sebasti...@embedded-brains.de>,
> freebsd-gn...@freebsd.org
> Subject: Re: usb/145455: USB debug support cannot be disabled
> Date: Wed, 7 Apr 2010 16:16:18 +0200
>
> On Wednesday 07 April 2010 14:49:43 Sebastian Huber wrote:
> > 145455
> >
>
> Hi,
>
> Your patch looks good and has been committed to USB P4.
>
> The patch to "usb_freebsd.h" was not committed, because we want to force
> debugging on by default until further unless you define USB_DEBUG=0 in your
> kernel config file.
>
> Please check and verify:
>
> http://p4db.freebsd.org/changeView.cgi?CH=176614&ignore=GO!
>
> --HPS
> _______________________________________________
> freeb...@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-usb
> To unsubscribe, send any mail to "freebsd-usb...@freebsd.org"

--
Sebastian Huber, embedded brains GmbH

Address : Obere Lagerstr. 30, D-82178 Puchheim, Germany
Phone : +49 89 18 90 80 79-6
Fax : +49 89 18 90 80 79-9
E-Mail : sebasti...@embedded-brains.de
PGP : Public key available on request.

Diese Nachricht ist keine geschДftliche Mitteilung im Sinne des EHUG.

------------------------------

Message: 7
Date: Wed, 7 Apr 2010 09:17:09 -0500
From: Vulpes Velox <v.v...@vvelox.net>
Subject: Re: usb touch screen support?
To: Norikatsu Shigemura <no...@FreeBSD.org>
Cc: freeb...@FreeBSD.org
Message-ID: <20100407091...@vixen42.vulpes.vvelox.net>
Content-Type: text/plain; charset="us-ascii"

On Sun, 5 Jul 2009 04:08:52 +0900
Norikatsu Shigemura <no...@FreeBSD.org> wrote:

> Hi.
>
> I got a usb touch screen device A.K.A. eGalax.
> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
> - - - - - - - - - - - - - ugen4.4: <USB TouchController eGalax
> Inc.> at usbus4, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON
> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
> - - - - - - - - - - - - -
>
> In this time, however, FreeBSD doesn't support usb touch
> screen. So I researched Linux's
> (drivers/input/touchscreen/usbtouchscreen.c) and NetBSD's (uep(4))
> implementations. It's too simple.
>
> I considered making modified ums(4) to adapt usb touch
> screen. But I noticed that ums(4) should be become a mouse subsystem
> like ucom(4), and I gave up:-). Anyone, do you have any
> idea?

Ever get any where?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 196 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-usb/attachments/20100407/6c308d8c/signature-0001.pgp

------------------------------

Message: 8
Date: Wed, 07 Apr 2010 07:06:42 -0700
From: Chris Telting <christo...@telting.org>
Subject: Syncronous Interrupt Transfer
To: u...@freebsd.org
Message-ID: <4BBC9172...@telting.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

Just learning the USB API.

Can someone point me to a driver to use as an example of a synchronous
call? Do
I need to use a mutex?

I have a device that that does the equivalent of control transfers over
an interrupt pipe.
So I need to send data, get status, send more data, get status again,
and then finally start
retrieving data; all using interrupt transfers. Been going over the
drivers in the kernel
and they are all looking to be doing async or synchronous back through
user mode.

------------------------------

Message: 9
Date: Wed, 7 Apr 2010 09:18:47 -0500
From: "Zane C.B." <v.v...@vvelox.net>
Subject: Re: WIP: usb touchscreen drivers
To: Volker <vol...@vwsoft.com>
Cc: u...@freebsd.org
Message-ID: <20100407091...@vixen42.vulpes.vvelox.net>
Content-Type: text/plain; charset="us-ascii"

On Tue, 10 Jun 2008 20:12:18 +0200
Volker <vol...@vwsoft.com> wrote:

> Hi everybody!
>
> I'm taking the chance and cross-posting this to the exciting,
> hopefully soon becoming busy, shiny new mailing list
> (freebsd-wip-status@ bcc'd, for those not already aware).
>
> Currently I'm working under contract for developing FreeBSD drivers
> for USB touchscreen devices. Before coding started, I've figured
> out the possible solutions to get a touchscreen device running
> under FreeBSD / X11 but haven't found much. We currently don't have
> any specialized drivers (but ums and uhid).
>
> More than worse: By default the ums driver is attaching to the
> device by default which has no support for devices reporting zero
> buttons and absolute coordinates. Currently OpenBSD has support for
> touchscreen devices but I found it difficult (or at least too much
> work) to port over wscons and replace syscons with that. Current
> touchscreen xf86-input drivers do partly support USB devices under
> Linux and I don't like to have the Xinput driver parse the USB
> protocol itself. Using a specialized kernel driver has some
> advantages IMO.
>
> Currently I'm having a basic, working driver (hence: WIP!), at
> kernel level (utouch) and a corresponding xf86-input-utouch driver.
> The first device supported is a Generaltouch ST6101U. So far, the
> device is working, the X pointer is following touches and button
> clicks are reported to X. Axis scaling is currently sub-optimal but
> I think I'll rework the scaling once more.
>
> What I would love to see: If you're having a USB connected
> touchscreen device laying around, I would love to see a krepdump
> [1] of that device to see how other devices are reporting.
> Especially, if you're having a multi-touch device, I would strongly
> love to see how this device reports data!
>
> BTW, it shouldn't be too difficult to enhance my driver
> infrastructure to also support tablet devices (also reporting
> absolute coordinates but also reporting button presses and some
> more functionality).
>
> As this work is under contract, I need to get approval to release
> the code but I'm pretty sure to get approval (BSD-licensed, of
> course). If you're interested in seeing USB touchscreen support for
> FreeBSD this way and have a device laying around, please contact me
> directly and I'll see how to support your device.

This ever go any where?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 196 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-usb/attachments/20100407/d3320bd7/signature-0001.pgp

------------------------------

Message: 10
Date: Wed, 7 Apr 2010 16:43:19 +0200
From: Hans Petter Selasky <hsel...@c2i.net>
Subject: Re: Syncronous Interrupt Transfer
To: freeb...@freebsd.org
Message-ID: <201004071643....@c2i.net>
Content-Type: Text/Plain; charset="iso-8859-1"

On Wednesday 07 April 2010 16:06:42 Chris Telting wrote:
> Just learning the USB API.
>
> Can someone point me to a driver to use as an example of a synchronous
> call? Do
> I need to use a mutex?

Hi,

Currently only control endpoints have a synchronous API to do requests of any
size. You can pass NULL for mutex, which basically means no mutex will be
dropped during sleeping periods.

BULK/INTERRUPT/ISOCHRONOUS are all asynchronous. However, in user-space,
libusb provides synchronous functions to read and write data.

> I have a device that that does the equivalent of control transfers over
> an interrupt pipe.
> So I need to send data, get status, send more data, get status again,
> and then finally start
> retrieving data; all using interrupt transfers. Been going over the
> drivers in the kernel
> and they are all looking to be doing async or synchronous back through
> user mode.

Probably we could make some convenience wrappers to do synchronous transfers
in the kernel. Else you need to make your own condition variable and sleep on
that until the USB transfer completes or fails.

If you think that a synchronous API for USB in the kernel is generally useful,
send me a patch and I'll commit it. Most drivers only use synchronous control
transfers.

--HPS

------------------------------

Message: 11
Date: Thu, 08 Apr 2010 01:22:37 +0300
From: Andriy Gapon <a...@icyb.net.ua>
Subject: Re: 7.3: instant panic upon connecting a umass
To: "Julian H. Stacey" <j...@berklix.com>
Cc: u...@freebsd.org, "Mikhail T." <mi+...@aldan.algebra.com>,
sta...@freebsd.org
Message-ID: <4BBD05AD...@icyb.net.ua>
Content-Type: text/plain; charset=KOI8-U

on 07/04/2010 14:20 Julian H. Stacey said the following:
> I wonder if it's eg a corrupt FS not being fsck'd first ?

Have you given a look to the backtrace that Mikhail had posted?
I think that it answers your question.

--
Andriy Gapon

------------------------------

Message: 12
Date: Thu, 08 Apr 2010 02:33:19 +0200
From: "Julian H. Stacey" <j...@berklix.com>
Subject: Re: 7.3: instant panic upon connecting a umass
To: Andriy Gapon <a...@icyb.net.ua>
Cc: u...@freebsd.org, "Mikhail T." <mi+...@aldan.algebra.com>,
sta...@freebsd.org
Message-ID: <201004080033....@fire.js.berklix.net>

Andriy Gapon wrote:
> on 07/04/2010 14:20 Julian H. Stacey said the following:
> > I wonder if it's eg a corrupt FS not being fsck'd first ?
>
> Have you given a look to the backtrace that Mikhail had posted?

Not looked. It was a URL, not text in mail.

> I think that it answers your question.

If I wasn't tired & out of depth, :-)
If mine was crashing, I'd first comment out devd entry to
identify & state to list what command fails, before trying kgdb.

I see
http://aldan.algebra.com/~mi/tmp/usb-crash.txt
has
Loaded symbols for /opt/modules/fuse.ko
man mount_fusefs

Oh well, not used Fuse, &
I've got my own crashes on 7 & 8.0-REL to amuse me ;-)
(mine from an encrypted usn stick with:
sync ... manual umount ... remove media ... then
devd.conf with
detach 1000 ...
action "gbde detach /dev/da0s2 ; ...
)

Cheers,
Julian
--
Julian Stacey: BSD Unix Linux C Sys Eng Consultants Munich http://berklix.com
Mail plain text, Not HTML quoted-printable Base64 http://www.asciiribbon.org

------------------------------

Message: 13
Date: Thu, 8 Apr 2010 02:31:50 GMT
From: mxxglgxt <rgiq...@jqbwsbfa.com>
Subject: usb/145484: mxxglgxt
To: freebsd-gn...@FreeBSD.org
Message-ID: <201004080231....@www.freebsd.org>

>Number: 145484
>Category: usb
>Synopsis: mxxglgxt
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: freebsd-usb
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: change-request
>Submitter-Id: current-users
>Arrival-Date: Thu Apr 08 02:40:04 UTC 2010
>Closed-Date:
>Last-Modified:
>Originator: mxxglgxt
>Release: mxxglgxt
>Organization:
mxxglgxt
>Environment:
mxxglgxt
>Description:
wfrljxnt http://bezfuvos.com pxxxzuyv wenrkfnh
>How-To-Repeat:
mxxglgxt
>Fix:
mxxglgxt

>Release-Note:
>Audit-Trail:
>Unformatted:

------------------------------

Message: 14
Date: Thu, 8 Apr 2010 03:04:12 GMT
From: h...@FreeBSD.org
Subject: Re: usb/145484: mxxglgxt
To: rgiq...@jqbwsbfa.com, h...@FreeBSD.org, freeb...@FreeBSD.org
Message-ID: <201004080304....@freefall.freebsd.org>

Synopsis: mxxglgxt

State-Changed-From-To: open->closed
State-Changed-By: hrs
State-Changed-When: Thu Apr 8 03:04:03 UTC 2010
State-Changed-Why:
spam.

http://www.freebsd.org/cgi/query-pr.cgi?pr=145484

------------------------------

Message: 15
Date: Thu, 8 Apr 2010 03:39:45 GMT
From: cywyynou <hpvp...@eprpgtyd.com>
Subject: usb/145493: cywyynou
To: freebsd-gn...@FreeBSD.org
Message-ID: <201004080339....@www.freebsd.org>

>Number: 145493
>Category: usb
>Synopsis: cywyynou
>Confidential: no
>Severity: critical
>Priority: medium
>Responsible: freebsd-usb
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: change-request
>Submitter-Id: current-users
>Arrival-Date: Thu Apr 08 03:40:05 UTC 2010
>Closed-Date:
>Last-Modified:
>Originator: cywyynou
>Release: cywyynou
>Organization:
cywyynou
>Environment:
cywyynou
>Description:
<a href="http://xgmfwrfp.com">xobllmky</a> [URL=http://pnpsesbc.com]njdwggal[/URL] nxilxvpe http://twuayihp.com tnhffyhq ejsmnijr
>How-To-Repeat:
cywyynou
>Fix:
cywyynou

>Release-Note:
>Audit-Trail:
>Unformatted:

------------------------------

Message: 16
Date: Thu, 8 Apr 2010 03:43:35 GMT
From: fkucedic <mtsu...@qjrfqxpv.com>
Subject: usb/145506: fkucedic
To: freebsd-gn...@FreeBSD.org
Message-ID: <201004080343....@www.freebsd.org>

>Number: 145506
>Category: usb
>Synopsis: fkucedic
>Confidential: no
>Severity: serious
>Priority: high
>Responsible: freebsd-usb
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: update
>Submitter-Id: current-users
>Arrival-Date: Thu Apr 08 03:50:05 UTC 2010
>Closed-Date:
>Last-Modified:
>Originator: fkucedic
>Release: fkucedic
>Organization:
fkucedic
>Environment:
fkucedic
>Description:
zfgvmuhe http://ruxfnnda.com ktiefeyl nsluvhdy
>How-To-Repeat:
fkucedic
>Fix:
fkucedic

>Release-Note:
>Audit-Trail:
>Unformatted:

------------------------------

Message: 17
Date: Thu, 8 Apr 2010 04:10:40 GMT
From: h...@FreeBSD.org
Subject: Re: usb/145493: cywyynou
To: hpvp...@eprpgtyd.com, h...@FreeBSD.org, freeb...@FreeBSD.org
Message-ID: <201004080410....@freefall.freebsd.org>

Synopsis: cywyynou

State-Changed-From-To: open->closed
State-Changed-By: hrs
State-Changed-When: Thu Apr 8 04:10:28 UTC 2010
State-Changed-Why:
spam.

http://www.freebsd.org/cgi/query-pr.cgi?pr=145493

------------------------------

Message: 18
Date: Thu, 8 Apr 2010 04:22:53 GMT
From: h...@FreeBSD.org
Subject: Re: usb/145506: fkucedic
To: mtsu...@qjrfqxpv.com, h...@FreeBSD.org, freeb...@FreeBSD.org
Message-ID: <201004080422....@freefall.freebsd.org>

Synopsis: fkucedic

State-Changed-From-To: open->closed
State-Changed-By: hrs
State-Changed-When: Thu Apr 8 04:22:45 UTC 2010
State-Changed-Why:
spam.

http://www.freebsd.org/cgi/query-pr.cgi?pr=145506

------------------------------

Message: 19
Date: Thu, 8 Apr 2010 10:55:44 GMT
From: Krutov Mikle <nekoex...@gmail.com>
Subject: usb/145513: New USB stack: no new devices after forced usb
flash detach
To: freebsd-gn...@FreeBSD.org
Message-ID: <201004081055....@www.freebsd.org>

>Number: 145513
>Category: usb
>Synopsis: New USB stack: no new devices after forced usb flash detach
>Confidential: no
>Severity: serious
>Priority: low
>Responsible: freebsd-usb
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Thu Apr 08 11:00:15 UTC 2010
>Closed-Date:
>Last-Modified:
>Originator: Krutov Mikle
>Release: 8.0-STABLE
>Organization:
>Environment:
FreeBSD takino.homeftp.org 8.0-STABLE FreeBSD 8.0-STABLE #0: Mon Mar 8 06:25:34 MSK 2010 ro...@takino.homeftp.org:/usr/obj/usr/src/sys/TAKINO amd64

>Description:
After detaching the mounted usb-flash device, no new usb-devices are detected.
USB controller is "device = 'SB700 USB OHCI1 Controller"
>How-To-Repeat:
1) attach (vfat-formated, did not test with other fs) flash device, mount it
2) detach without umounting
3) try to attach another usb-device
4) see no new devices, no dmesg messages, nothing
>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:

------------------------------

Message: 20
Date: Thu, 8 Apr 2010 13:52:50 +0200
From: Hans Petter Selasky <hsel...@c2i.net>
Subject: Re: usb/145513: New USB stack: no new devices after forced
usb flash detach
To: freeb...@freebsd.org
Cc: freebsd-gn...@freebsd.org
Message-ID: <201004081352....@c2i.net>
Content-Type: Text/Plain; charset="iso-8859-15"

On Thursday 08 April 2010 12:55:44 Krutov Mikle wrote:
> >Number: 145513
> >Category: usb
> >Synopsis: New USB stack: no new devices after forced usb flash
> > detach Confidential: no
> >Severity: serious
> >Priority: low
> >Responsible: freebsd-usb
> >State: open
> >Quarter:
> >Keywords:
> >Date-Required:
> >Class: sw-bug
> >Submitter-Id: current-users
> >Arrival-Date: Thu Apr 08 11:00:15 UTC 2010
> >Closed-Date:
> >Last-Modified:
> >Originator: Krutov Mikle
> >Release: 8.0-STABLE
> >Organization:
> >Environment:
>
> FreeBSD takino.homeftp.org 8.0-STABLE FreeBSD 8.0-STABLE #0: Mon Mar 8
> 06:25:34 MSK 2010 ro...@takino.homeftp.org:/usr/obj/usr/src/sys/TAKINO
> amd64
>
> >Description:
>
> After detaching the mounted usb-flash device, no new usb-devices are
> detected. USB controller is "device = 'SB700 USB OHCI1 Controller"
>
> >How-To-Repeat:
>
> 1) attach (vfat-formated, did not test with other fs) flash device, mount
> it 2) detach without umounting
> 3) try to attach another usb-device
> 4) see no new devices, no dmesg messages, nothing
>

Hi,

That's because the UMASS detach is hanging, most likely.

Try to break into the kernel and get a backtrace.

--HPS

------------------------------

Message: 21
Date: Thu, 8 Apr 2010 12:00:19 GMT
From: Hans Petter Selasky <hsel...@c2i.net>
Subject: Re: usb/145513: New USB stack: no new devices after forced
usb flash detach
To: freeb...@FreeBSD.org
Message-ID: <201004081200....@freefall.freebsd.org>

The following reply was made to PR usb/145513; it has been noted by GNATS.

From: Hans Petter Selasky <hsel...@c2i.net>
To: freeb...@freebsd.org
Cc: Krutov Mikle <nekoex...@gmail.com>,
freebsd-gn...@freebsd.org
Subject: Re: usb/145513: New USB stack: no new devices after forced usb flash detach
Date: Thu, 8 Apr 2010 13:52:50 +0200

------------------------------

Message: 22
Date: Thu, 8 Apr 2010 19:29:43 +0200
From: Hans Petter Selasky <hsel...@c2i.net>
Subject: Re: usb/145513: New USB stack: no new devices after forced
usb flash detach
To: Mikle Krutov <nekoex...@gmail.com>
Cc: freebsd-gn...@freebsd.org, freeb...@freebsd.org
Message-ID: <201004081929....@c2i.net>
Content-Type: Text/Plain; charset="iso-8859-1"

Add:

options KDB # Enable kernel debugger support.
options DDB # Support DDB.
options GDB # Support remote GDB.

When it hangs, enter this from the console:

sysctl debug.kdb.panic=1

Type

alltrace

bt all

or something similar.

Type "continue" when you are finished.

You can also use CTRL+ALT+ESC key combination.

--HPS

------------------------------

Message: 23
Date: Thu, 8 Apr 2010 17:40:03 GMT
From: Hans Petter Selasky <hsel...@c2i.net>
Subject: Re: usb/145513: New USB stack: no new devices after forced
usb flash detach
To: freeb...@FreeBSD.org
Message-ID: <201004081740....@freefall.freebsd.org>

The following reply was made to PR usb/145513; it has been noted by GNATS.

From: Hans Petter Selasky <hsel...@c2i.net>
To: Mikle Krutov <nekoex...@gmail.com>
Cc: freeb...@freebsd.org,
freebsd-gn...@freebsd.org
Subject: Re: usb/145513: New USB stack: no new devices after forced usb flash detach
Date: Thu, 8 Apr 2010 19:29:43 +0200

On Thursday 08 April 2010 19:14:03 Mikle Krutov wrote:
> On Thu, Apr 08, 2010 at 01:52:50PM +0200, Hans Petter Selasky wrote:
> > Hi,
> >
> > That's because the UMASS detach is hanging, most likely.
> >
> > Try to break into the kernel and get a backtrace.
> >
> > --HPS
>
> Hi,
> I unfortunately could not find any info about how do i do this. Could
> you provide me some link?
>

Add:

options KDB # Enable kernel debugger support.
options DDB # Support DDB.
options GDB # Support remote GDB.

When it hangs, enter this from the console:

sysctl debug.kdb.panic=1

Type

alltrace

bt

bt all

or something similar.

Type "continue" when you are finished.

You can also use CTRL+ALT+ESC key combination.

--HPS

------------------------------

Message: 24
Date: Thu, 8 Apr 2010 21:14:03 +0400
From: Mikle Krutov <nekoex...@gmail.com>
Subject: Re: usb/145513: New USB stack: no new devices after forced
usb flash detach
To: Hans Petter Selasky <hsel...@c2i.net>
Cc: freebsd-gn...@freebsd.org, freeb...@freebsd.org
Message-ID: <20100408171...@takino.homeftp.org>
Content-Type: text/plain; charset=us-ascii

On Thu, Apr 08, 2010 at 01:52:50PM +0200, Hans Petter Selasky wrote:
> Hi,
>
> That's because the UMASS detach is hanging, most likely.
>
> Try to break into the kernel and get a backtrace.
>
> --HPS
Hi,
I unfortunately could not find any info about how do i do this. Could
you provide me some link?

--
Wbr,
Krutov Mikle

------------------------------

Message: 25
Date: Thu, 8 Apr 2010 17:50:03 GMT
From: Mikle Krutov <nekoex...@gmail.com>
Subject: Re: usb/145513: New USB stack: no new devices after forced
usb flash detach
To: freeb...@FreeBSD.org
Message-ID: <201004081750....@freefall.freebsd.org>

The following reply was made to PR usb/145513; it has been noted by GNATS.

From: Mikle Krutov <nekoex...@gmail.com>
To: Hans Petter Selasky <hsel...@c2i.net>
Cc: freeb...@freebsd.org, freebsd-gn...@freebsd.org
Subject: Re: usb/145513: New USB stack: no new devices after forced usb
flash detach
Date: Thu, 8 Apr 2010 21:14:03 +0400

------------------------------

Message: 26
Date: Thu, 8 Apr 2010 23:22:59 GMT
From: yzhxfsnj <iaym...@tnstcxga.com>
Subject: usb/145540: yzhxfsnj
To: freebsd-gn...@FreeBSD.org
Message-ID: <201004082322....@www.freebsd.org>

>Number: 145540
>Category: usb
>Synopsis: yzhxfsnj
>Confidential: no
>Severity: critical
>Priority: medium
>Responsible: freebsd-usb
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: change-request
>Submitter-Id: current-users
>Arrival-Date: Thu Apr 08 23:30:03 UTC 2010
>Closed-Date:
>Last-Modified:
>Originator: yzhxfsnj
>Release: yzhxfsnj
>Organization:
yzhxfsnj
>Environment:
yzhxfsnj
>Description:
wfuyqbio http://iqoggcfl.com spokmcbv iugolzwa [URL=http://dgcmaiiu.com]nfxmqwtb[/URL] <a href="http://wqottiln.com">xluivcdc</a>
>How-To-Repeat:
yzhxfsnj
>Fix:
yzhxfsnj

>Release-Note:
>Audit-Trail:
>Unformatted:

------------------------------

Message: 27
Date: Thu, 8 Apr 2010 23:25:08 GMT
From: jqwgjvle <xdhr...@jrnnlnfj.com>
Subject: usb/145544: jqwgjvle
To: freebsd-gn...@FreeBSD.org
Message-ID: <201004082325....@www.freebsd.org>

>Number: 145544
>Category: usb
>Synopsis: jqwgjvle
>Confidential: no
>Severity: critical
>Priority: high
>Responsible: freebsd-usb
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: doc-bug
>Submitter-Id: current-users
>Arrival-Date: Thu Apr 08 23:30:04 UTC 2010
>Closed-Date:
>Last-Modified:
>Originator: jqwgjvle
>Release: jqwgjvle
>Organization:
jqwgjvle
>Environment:
jqwgjvle
>Description:
qbhdfrxy http://eubtbnbj.com jkaubgpt mjtylvbi
>How-To-Repeat:
jqwgjvle
>Fix:
jqwgjvle

>Release-Note:
>Audit-Trail:
>Unformatted:

------------------------------

Message: 28
Date: Thu, 8 Apr 2010 23:25:33 GMT
From: ubnbamwa <mczg...@hkqwozrl.com>
Subject: usb/145545: ubnbamwa
To: freebsd-gn...@FreeBSD.org
Message-ID: <201004082325....@www.freebsd.org>

>Number: 145545
>Category: usb
>Synopsis: ubnbamwa
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: freebsd-usb
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: change-request
>Submitter-Id: current-users
>Arrival-Date: Thu Apr 08 23:30:05 UTC 2010
>Closed-Date:
>Last-Modified:
>Originator: ubnbamwa
>Release: ubnbamwa
>Organization:
ubnbamwa
>Environment:
ubnbamwa
>Description:
mtstoerw http://yezmkgdw.com zokuhvcg ndjfrvhz
>How-To-Repeat:
ubnbamwa
>Fix:
ubnbamwa

>Release-Note:
>Audit-Trail:
>Unformatted:

------------------------------

Message: 29
Date: Fri, 9 Apr 2010 01:19:49 GMT
From: h...@FreeBSD.org
Subject: Re: usb/145540: yzhxfsnj
To: iaym...@tnstcxga.com, h...@FreeBSD.org, freeb...@FreeBSD.org
Message-ID: <201004090119....@freefall.freebsd.org>

Synopsis: yzhxfsnj

State-Changed-From-To: open->closed
State-Changed-By: hrs
State-Changed-When: Fri Apr 9 01:19:42 UTC 2010
State-Changed-Why:
spam.

http://www.freebsd.org/cgi/query-pr.cgi?pr=145540

------------------------------

Message: 30
Date: Fri, 9 Apr 2010 01:20:31 GMT
From: h...@FreeBSD.org
Subject: Re: usb/145544: jqwgjvle
To: xdhr...@jrnnlnfj.com, h...@FreeBSD.org, freeb...@FreeBSD.org
Message-ID: <201004090120....@freefall.freebsd.org>

Synopsis: jqwgjvle

State-Changed-From-To: open->closed
State-Changed-By: hrs
State-Changed-When: Fri Apr 9 01:20:24 UTC 2010
State-Changed-Why:
spam.

http://www.freebsd.org/cgi/query-pr.cgi?pr=145544

------------------------------

Message: 31
Date: Fri, 9 Apr 2010 01:20:43 GMT
From: h...@FreeBSD.org
Subject: Re: usb/145545: ubnbamwa
To: mczg...@hkqwozrl.com, h...@FreeBSD.org, freeb...@FreeBSD.org
Message-ID: <201004090120....@freefall.freebsd.org>

Synopsis: ubnbamwa

State-Changed-From-To: open->closed
State-Changed-By: hrs
State-Changed-When: Fri Apr 9 01:20:34 UTC 2010
State-Changed-Why:
spam.

http://www.freebsd.org/cgi/query-pr.cgi?pr=145545

------------------------------

Message: 32
Date: Fri, 9 Apr 2010 05:46:37 GMT
From: lin...@FreeBSD.org
Subject: Re: usb/145527: Re: usb/141313: [usb8] nvidia USB 2.0
controller - stops copying on USB
To: adr...@bocaniciu.ro, lin...@FreeBSD.org, gnats...@FreeBSD.org,
freeb...@FreeBSD.org
Message-ID: <201004090546....@freefall.freebsd.org>

Old Synopsis: Re:%20usb/141313:%20[usb8]%20nvidia%20USB%202.0%20controller%20-%20stops%20copying%20on%20USB
New Synopsis: Re: usb/141313: [usb8] nvidia USB 2.0 controller - stops copying on USB

State-Changed-From-To: open->closed
State-Changed-By: linimon
State-Changed-When: Fri Apr 9 05:44:56 UTC 2010
State-Changed-Why:
Misfiled followup to usb/141313; content migrated.

Responsible-Changed-From-To: gnats-admin->freebsd-usb
Responsible-Changed-By: linimon
Responsible-Changed-When: Fri Apr 9 05:44:56 UTC 2010
Responsible-Changed-Why:

http://www.freebsd.org/cgi/query-pr.cgi?pr=145527

------------------------------

Message: 33
Date: Fri, 9 Apr 2010 06:48:14 GMT
From: tho...@FreeBSD.org
Subject: Re: usb/141313: [usb8] nvidia USB 2.0 controller - stops
copying on USB [regression]
To: janm...@gdi.cz, tho...@FreeBSD.org, freeb...@FreeBSD.org,
tho...@FreeBSD.org
Message-ID: <201004090648....@freefall.freebsd.org>

Synopsis: [usb8] nvidia USB 2.0 controller - stops copying on USB [regression]

State-Changed-From-To: open->feedback
State-Changed-By: thompsa
State-Changed-When: Fri Apr 9 06:47:06 UTC 2010
State-Changed-Why:
This can be tested by upgrading to 8-stable or applying http://people.freebsd.org/~thompsa/r206302.diff

Responsible-Changed-From-To: freebsd-usb->thompsa
Responsible-Changed-By: thompsa
Responsible-Changed-When: Fri Apr 9 06:47:06 UTC 2010
Responsible-Changed-Why:
This can be tested by upgrading to 8-stable or applying http://people.freebsd.org/~thompsa/r206302.diff

http://www.freebsd.org/cgi/query-pr.cgi?pr=141313

------------------------------

Message: 34
Date: Fri, 9 Apr 2010 08:30:06 GMT
From: Nick Hibma <ni...@van-laarhoven.org>
Subject: Re: usb/145237: [usbdevs] [patch] Add support for Matrix
Orbital MOU display
To: freeb...@FreeBSD.org
Message-ID: <201004090830....@freefall.freebsd.org>

The following reply was made to PR usb/145237; it has been noted by GNATS.

From: Nick Hibma <ni...@van-laarhoven.org>
To: bug-fo...@FreeBSD.org, ni...@anywi.com
Cc:
Subject: Re: usb/145237: [usbdevs] [patch] Add support for Matrix Orbital MOU display
Date: Fri, 9 Apr 2010 10:22:44 +0200

This has been committed to 7-STABLE.

------------------------------

Message: 35
Date: Fri, 9 Apr 2010 20:00:02 +0530
From: Rohit Grover <rgro...@gmail.com>
Subject: USB Keyboard puzzle
To: freeb...@freebsd.org
Message-ID:
<h2p426bed111004090730p5...@mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"

Hello Dear Hackers,

This is about a puzzling behaviour which has affected me for quite
some time now and has caused far too many unwanted reboots on my
Macbook (running FreeBSD).

The problem appeared around when I transitioned from using 8.0/Release
8.0/STABLE; although I am not a 100% sure of that. If I were to switch
back to 8.0/Release, things would work normally; but then many
significant and necessary changes have gone into 8.0/STABLE and I do
not have the option of reverting to 8.0/Release.

It has to do with the software around the USB keyboard. When booting a
derivative of 8.0/Stable, about half the time my laptop boots into a
state where the keyboard is unresponsive; i.e. keystrokes have no
effect; and thus this condition forces me into a wasteful reboot. This
state is very likely to reproduce if I do a cold boot.
I have also discovered that if I boot the laptop with MacOSX, and then
subsequently reboot into FreeBSD, I have a high chance of getting a
usable keyboard.

I had previously suspected changes to code in the ukbd driver. But now
I have confirmed for myself that ukbd is sane--I did this by adding
printfs to the data-flow path, and ensured that the read_char()
device-switch handler within ukbd is correctly able to return key
scan-codes even when my keyboard appears to be dead.

I have also noticed that in the cases where my keyboard appears to be
unresponsive, ukbd attaches as two separate instances: ukbd0 and
ukbd1:

<verbatim>
Apr 9 19:20:35 macbook kernel: ugen0.2: <vendor 0x05ac> at usbus0
Apr 9 19:20:35 macbook kernel: ukbd0: <vendor 0x05ac product 0x1000,
class 0/0, rev 2.00/19.65, addr 2> on usbus0
Apr 9 19:20:35 macbook kernel: kbd0 at ukbd0
Apr 9 19:20:35 macbook kernel: Root mount waiting for: usbus6
Apr 9 19:20:35 macbook kernel: Trying to mount root from ufs:/dev/ad6p3a
Apr 9 19:20:35 macbook kernel: ugen5.2: <Apple Computer, Inc.> at usbus5
Apr 9 19:20:35 macbook kernel: GEOM_PART: Partition 'ad6p3' not
suitable for kernel dumps (wrong type?)
Apr 9 19:20:35 macbook kernel: ugen5.3: <Apple Computer> at usbus5
Apr 9 19:20:35 macbook kernel: ukbd1: <Apple Internal Keyboard> on usbus5
Apr 9 19:20:35 macbook kernel: kbd1 at ukbd1
</verbatim>

whereas when the keyboard boots in an OK state, I see the following
during boot--there is only ukbd0 and no ukbd1:

<verbatim>
Apr 9 19:23:21 macbook kernel: ugen5.3: <Apple Computer> at usbus5
Apr 9 19:23:21 macbook kernel: ukbd0: <Apple Internal Keyboard> on usbus5
Apr 9 19:23:21 macbook kernel: kbd0 at ukbd0
</verbatim>

I have attached my config file, and the dmesg dump from the good and bad cases.

Could you please help me figure out what's going on with my keyboard?

thanks,
Rohit.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: MACBOOK
Type: application/octet-stream
Size: 12783 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-usb/attachments/20100409/cb05e60c/MACBOOK.obj
-------------- next part --------------
A non-text attachment was scrubbed...
Name: dmesg.good
Type: application/octet-stream
Size: 17147 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-usb/attachments/20100409/cb05e60c/dmesg.obj
-------------- next part --------------
A non-text attachment was scrubbed...
Name: dmesg.bad
Type: application/octet-stream
Size: 16414 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-usb/attachments/20100409/cb05e60c/dmesg-0001.obj

------------------------------

End of freebsd-usb Digest, Vol 283, Issue 2
*******************************************

0 new messages