Hi David,
> > I found out that usb_set_configuration() was removed from the USB API by
> > you. I want to rewrite my bfusb driver to use it and not playing tricks
> > to get this working anymore. Can you give me a hint how to change the
> > configuration from within a kernel driver?
>
> It's stil
Al Borchers wrote:
Phil Dibowitz wrote:
Al Borchers wrote:
Is
the app using ppp to connect with the phone, by any chance?
Nope ...
Then probably the app is opening the port O_NONBLOCK but not
expecting short writes.
After confirming that is indeed what they're doing, I've gone ahead and
explaine
Hi,
as far as I understood now, it is not of great help to "snoop" the traffic
between the cam and Windoze - isn't it? Because when usbsnoopy
is working, the initial setup is already done - am I right?
As Windoze98 does not support the USB storage stuff "out-of-the-box",
KonicaMinolta ships a "dI
Alan Stern wrote:
What do you think about the problem of stalling the bulk-out endpoint when
the host sends too much data? Maybe this hasn't caused you any
difficulty yet. The problem is that there's a race.
What'd be the consequence of just not using bulk stalls?
- Dave
Matan Ziv-Av wrote:
Hello,
I am trying to get USB working on Jornada 820, which uses SA1101. There
is already a driver in the kernel for OHCI on SA, which is similar
to 1101, so I do this by changing the driver.
This method works on kernel 2.4 (2.4.19-hh36 from handhelds.org), but on
k
Marcel Holtmann wrote:
Hi David,
I found out that usb_set_configuration() was removed from the USB API by
you. I want to rewrite my bfusb driver to use it and not playing tricks
to get this working anymore. Can you give me a hint how to change the
configuration from within a kernel driver?
It's sti
Todd Fischer wrote:
I am developing a UDC for the TI DM270 which has a UDC tailored for a
digital camera use model. I had to create separate ep1in and ep1out
endpoint instead of a single bidi ep to make file_storage.c (and zero.c)
happy.
Was that particularly troublesome? That particular hardwar
Hi David,
I found out that usb_set_configuration() was removed from the USB API by
you. I want to rewrite my bfusb driver to use it and not playing tricks
to get this working anymore. Can you give me a hint how to change the
configuration from within a kernel driver?
Regards
Marcel
-
> -Original Message-
> From: Diego Dompe [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, July 27, 2004 2:42 PM
> To: Alan Stern
>
> > What do you think about the problem of stalling the bulk-out
> endpoint when
> > the host sends too much data? Maybe this hasn't caused you any
> > difficulty
Alan,
On Tue, 2004-07-27 at 15:49 -0400, Alan Stern wrote:
> That's a problem in the controller driver. Which driver are you using?
> It should include something like this in its usb_gadget_register_driver()
> routine (this is copied from net2280.c):
>
> dev->gadget.dev.driver = &driver
Greg and Pete:
According to Jonas Fährmann, the very first entry in unusual_devs.h isn't
needed. In fact, I can't tell why it was there in the first place...
unless some earlier device in the product line had incorrect descriptor
values.
Alan Stern
On Mon, 26 Jul 2004, Jonas Fährmann wrote:
On Tue, 27 Jul 2004, Diego Dompe wrote:
> The driver registration logic was producing the kernel to get NULL
> pointer references.
See below.
> > You moved the code that registers the LUN devices into
> > fsg_bind(). This change looks correct; although there is
> > a comment stating
> This is just the same behavior as you saw before making any changes,
> right?
yes - except the "unneeded SubClass and Protocol entries in unusual_devs.h", it says
"Initializing USB Mass Storage driver..." instead - thanks to your patch :)
> Actually I suspect the device has the strange behavi
Hi Alan,
> What was wrong with the registration logic and how did it crash your
> kernel? In your patch I see two changes:
The driver registration logic was producing the kernel to get NULL
pointer references.
> You moved the code that registers the LUN devices into
> fsg_bind().
On Tue, 27 Jul 2004, Todd Fischer wrote:
> Hi,
>
> We ran into a few problems trying to use file backed storage on 2.6.
What were your problems?
> Attached is the patch file to the 1.9 version of the Linux 2.6
> file_storage.c file, which makes the following changes:
>
> - Fix the registration
On Tue, 27 Jul 2004 10:37:25 -0400 (EDT)
Alan Stern <[EMAIL PROTECTED]> wrote:
> > On Tue, 27 Jul 2004 00:52:52 -0500
> > Dmitry Torokhov <[EMAIL PROTECTED]> wrote:
> >
> > > Got the following OOps when when turning off a all-in-one USB printer/scanner
> > > after scanning an image with Xsane and
Greg,
This patch adds support for the FTDI FT2232C USB to dual serial port
converter to the ftdi_sio driver.
The patch is based on a fork of the 2.4 ftdi_sio driver by Steven
Turner of FTDI, and a preliminary port of these changes to the 2.6
ftdi_sio driver by Rus V. Brushkoff. I've tidied it
Hi Alan,
I commented out the lines you told me to, rebuilt the kernel and gave it another try
after rebooting.
Dmesg now says:
usb 3-1: new full speed USB device using address 2
usb 3-1: device not accepting address 2, error -84
usb 3-1: new full speed USB device using address 3
Initializing USB
Hi,
We ran into a few problems trying to use file backed storage on 2.6.
Attached is the patch file to the 1.9 version of the Linux 2.6
file_storage.c file, which makes the following changes:
- Fix the registration logic that was crashing the kernel.
- Move the removable parameter to be used on n
On Mon, 26 Jul 2004, Jonas Fährmann wrote:
> > Can you send a copy of your /proc/bus/usb/devices file with the drive
> >plugged in?
> T: Bus=03 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 6 Spd=12 MxCh= 0
> D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
> P: Vendor=03ee ProdID= Rev=
On Mon, 26 Jul 2004, Sven-Olof Klasson wrote:
> Alan, many thanks for all your efforts. I really appreciate it.
>
> I tried this patch but unfortually it does not make any diffrence. I had also
> the first patch installed, but not the patch with the two msleep()
>
> Regards,
> Sven-Olof
You sti
On Tue, 27 Jul 2004, Duncan Sands wrote:
> don't you need some special hardware to turn yourself into a gadget? How
> does it work? - it sounds very useful.
You do indeed need special hardware. If you've got a PXA-based system
(like the Zaurus) then you're already set. If you've got a regular
On Tue, 27 Jul 2004, Pete Zaitcev wrote:
> On Tue, 27 Jul 2004 00:52:52 -0500
> Dmitry Torokhov <[EMAIL PROTECTED]> wrote:
>
> > Got the following OOps when when turning off a all-in-one USB printer/scanner
> > after scanning an image with Xsane and leaving Xsane window open.
>
> > EIP is at usb
Hello adsynori,
thanks for your reply!
I check out the tip you referred to, and indead there is a "ChipID:6620"
there, sorry for that. :)
But I still got some errors while I vidcated the test picture.
__
[EMAIL PROTECTED] jerry]$./vid
From: Dmitry Torokhov
Date: 2004-07-20 4:04:47
>Hopefully if send the patch directly to you you will be able to apply
>it. Just save entire mail as a text and feed it to patch.
>
>Please let me know if it works for you.
I suffered the "pointer goes to the upper left corner" problem as
Hi Alan,
> I changed the file_storage gadget so that it would send full 255-byte
> replies (with type = length = 0) to string fetches when the requested
> length was 255 bytes and the string number was > 0. It's hard to tell
> whether Windows liked it or not, because in any case the descriptors w
On Tue, 27 Jul 2004 00:52:52 -0500
Dmitry Torokhov <[EMAIL PROTECTED]> wrote:
> Got the following OOps when when turning off a all-in-one USB printer/scanner
> after scanning an image with Xsane and leaving Xsane window open.
> EIP is at usb_buffer_free+0x1a/0x50 [usbcore]
> Process ptal-mlcd (pi
Phil Dibowitz wrote:
OK, happy to do. Though the only other thing there is:
My appologies, the logs in my previous email were from another syncing
program that has a similar error -- though it's only backing up, so I
want to be consistent in the information I provide. Here's debug info
from mult
28 matches
Mail list logo
