Hi.
Summary: I ended up with an unkillable jpilot process and an
unloadable visor module.
With a vanilla 2.4.22, I was synchronizing my Tungsten C when I
removed it from the cradle. J-Pilot 0.99.6 said:
ReadDBList returned = -1
J-Pilot: sync PID = 3343
J-Pilot: press the hotsync button on
This is the Postfix program at host vpop-2.mc.mpls.visi.com.
I'm sorry to have to inform you that the message returned
below could not be delivered to one or more destinations.
For further assistance, please send mail to
If you do so, please include this problem report. You can
delete your own
On Sat, Oct 11, 2003 at 06:10:14PM +0200, Benjamin Herrenschmidt wrote:
> Hi Folks !
>
> There's a small issue with drivers/usb/serial/keyspan_usa90msg.h
>
> The definition for MSR_RI conflicts with some PowerPC CPU definition
> (MSR is the Machine State Register on PPC and processor.h defines
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> See the PXA UDC docs, figure 12.5 ... you need a GPIOx-controlled pullup
> on UDC+ to disconnect under software control (forcing re-enumeration).
No sooner did I post my response than did I realize this that that may all be
well and good, but that's
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> See the PXA UDC docs, figure 12.5 ... you need a GPIOx-controlled pullup
> on UDC+ to disconnect under software control (forcing re-enumeration).
D'oh, just realized that I never implemented that on h3900. /me stupid
> And a GPIOn-triggered IRQ to
Joshua Wise wrote:
It seems that if the UDC is already enabled and is connected already (for
instance if I was previously running linux and I jump into a new kernel),
when I disconnect and reconnect the USB cable, nothing happens (my g_char
driver isn't notified.)
Thoughts?
See the PXA UDC docs
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all,
It seems that if the UDC is already enabled and is connected already (for
instance if I was previously running linux and I jump into a new kernel),
when I disconnect and reconnect the USB cable, nothing happens (my g_char
driver isn't notif
Am Samstag, 11. Oktober 2003 20:01 schrieb Willy Gardiol:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
>
> This is the point:
> i have an usb floppy driver and a multi-card flash reader/writer.
>
> The floppy does not work with "probe for all luns" enabled
> But i cannot access any port e
You can add your multicard reader manually and leave that option off.
On Sat, 11 Oct 2003, Willy Gardiol wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
>
> This is the point:
> i have an usb floppy driver and a multi-card flash reader/writer.
>
> The floppy does not work with "probe f
usb 3-3: configuration #1 chosen from 2 choices
drivers/usb/class/cdc-acm.c: need inactive config #2
drivers/usb/class/cdc-acm.c: need inactive config #2
Until we get more intelligence somewhere, do this:
# cd /sys/bus/usb/devices/3-3
# echo '2' > bConfigurationValue
#
That makes the devi
yay, yet another release that doesn't have the bug
fixed:(
http://bugme.osdl.org/show_bug.cgi?id=1229
__
Do you Yahoo!?
The New Yahoo! Shopping - with improved product search
http://shopping.yahoo.com
---
This
Hello,
sorry to disturb here, but I couldn't find any help in the users mailing
list, so, as a last resort, I try with developers
I am trying to use a Superdisk Imation
LS-120 drive, that, as far as I can read on www.linux-usb.org, should be
fully supported by usb mass storage driver.
I have previ
Paolo Ornati wrote:
[Please CC me, I'm not subscribed]
Some days ago I have wrote to this list to expose a problem I have using
kernel 2.6.0-textX + stv680 + UHCI_HCD driver...
the subject was: "USB-Problems with uhci_hcd + V4L + stv680 driver"
http://marc.theaimsgroup.com/?l=linux-usb-devel&m=106
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
This is the point:
i have an usb floppy driver and a multi-card flash reader/writer.
The floppy does not work with "probe for all luns" enabled
But i cannot access any port except the first one on my multi-card device if i
do not enable "probe for a
Petr Olivka wrote:
Hi !
I have still problem with USB devices. When I plug in any devices, then
USB require continuous busmaster activity. This behaviour disable
powersave state for CPU in kernel 2.6.test7
When I have loaded modules usb-core, uhci-hcd, hid, all work fine.
But whn I plug in mous
Michal Sojka wrote:
Hi,
I tried to rewrite USB 2.0 isochronous transfer support and here is the
patch against 2.6.0-test7.
Cool! That's needed some attention, I'll have a look at this.
And I've really been hoping someone would help out in this area.
I tested this code with our measuring device
Oliver Neukum wrote:
Am Dienstag, 7. Oktober 2003 22:10 schrieb David Brownell:
default:
- /* BKL used here to protect against changing the binding
-* of this driver to this device, as well as unloading its
-* driver module.
-*/
Hi Folks !
There's a small issue with drivers/usb/serial/keyspan_usa90msg.h
The definition for MSR_RI conflicts with some PowerPC CPU definition
(MSR is the Machine State Register on PPC and processor.h defines
MSR_RI globally). This definition doesn't seem to be used in any .c
in drivers/usr/ser
[Please CC me, I'm not subscribed]
Some days ago I have wrote to this list to expose a problem I have using
kernel 2.6.0-textX + stv680 + UHCI_HCD driver...
the subject was: "USB-Problems with uhci_hcd + V4L + stv680 driver"
http://marc.theaimsgroup.com/?l=linux-usb-devel&m=106493648430605&w=2
Sh
Hi,
I tried to rewrite USB 2.0 isochronous transfer support and here is the
patch against 2.6.0-test7.
I tested this code with our measuring device and I was able to do
high-speed high-bandwidth transfer (IN transactions) continuously for
very long time. In my opinion there are still some thin
It's quite easy to accidentally miss this option out. I think it makes
sense to default it to yes if HID support is enabled.
comments ?
regards
john
Index: linux-cvs/drivers/usb/input/Kconfig
===
RCS file: /home/cvs/linux-2.5/driv
Am Dienstag, 7. Oktober 2003 22:10 schrieb David Brownell:
> default:
> - /* BKL used here to protect against changing the binding
> -* of this driver to this device, as well as unloading its
> -* driver module.
> -*/
> -
Am Freitag, 10. Oktober 2003 17:00 schrieb David Brownell:
> Oliver Neukum wrote:
> >>So this is a "feedback please". Essentially all of
> >>the changes are consequences of the first one, to remove
> >>usb-internal state duplicating driver model state.
> >
> >
> > Looking very cool. You are repl
Am Samstag, 11. Oktober 2003 04:09 schrieb Greg KH:
> On Fri, Oct 10, 2003 at 06:18:04PM -0700, David Brownell wrote:
> > Greg KH wrote:
> > >On Tue, Oct 07, 2003 at 01:10:02PM -0700, David Brownell wrote:
> > >
> > >>So this is a "feedback please". Essentially all of
> > >>the changes are consequ
24 matches
Mail list logo
