On Wed, 9 Mar 2005 20:34:39 -0800 Greg KH <[EMAIL PROTECTED]> wrote:
> Did you try the usbmon code? It's in the -mm releases and now in
> Linus's tree. It will show up in the next main release too. It's much
> better at watching the usb data than the printk() method.
Well, usbmon is better in
On Wednesday 09 March 2005 4:02 pm, Shiju Mathew wrote:
> Hi,
> I have tried the two patches singly and together . But it did not
> resolve the usb audio problem.
Well that's annoying. Thanks for trying those; I can't really do
much to track this down, since I can't reproduce this. Can you do me
On Wednesday 09 March 2005 7:16 pm, peng peng wrote:
> I wrote code to enable uhci portsc ,but not success ,
> why ? My code is as follow :
>
> procedure pci_enable;
> var okay:boolean;
> result:word;
> begin
> ...
What language is that? Linux kernel code is written in C ... and
there'
On Thu, Mar 10, 2005 at 11:15:35AM +1000, Glen Harris wrote:
> > This chip, DIB3000P, is supported by the dvb driver, however this
> particular
> > implimentation is different. Normally, the device appears on the usb bus
> as
> > a particular VID/PID, the firmware is downloaded, the device discon
I want to send packet to usb device by frame list
defined in UHCI, when I define a transferdescriptor in
framelist and the send it , when that ok ,how can I
get the answer data for it . When get answer data in
interrupt service , how can I know which packet cause
this interrupt ?
Thanks :)
Regar
I wrote code to enable uhci portsc ,but not success ,
why ? My code is as follow :
procedure pci_enable;
var okay:boolean;
result:word;
begin
if
readPCIRegisterWord($4,USBBusNumber,USBFunctionNumber,result)
then
begin
result := result and $05; { bus master enable/
> This chip, DIB3000P, is supported by the dvb driver, however this particular
> implimentation is different. Normally, the device appears on the usb bus as
> a particular VID/PID, the firmware is downloaded, the device disconnects
> itself from the bus and reconnects with the PID incremented by on
Christopher Li wrote:
Nice to heard that it works with VMware. I might just add the USB IO logging
feature to VMware so people don't have to sniffer VMware again.
That would be great. The device initalizes, I can tune the stations, but
watching TV is impossible as the framerate is about one frame e
Nice to heard that it works with VMware. I might just add the USB IO logging
feature to VMware so people don't have to sniffer VMware again.
You need to have more information on what is happening in the IO.
I think you are not interested in the IO that upload the firmware.
You might want to consi
Hi,
I have tried the two patches singly and together . But it did not
resolve the usb audio problem.
Shiju
On Wed, 9 Mar 2005 09:12:57 -0800, David Brownell <[EMAIL PROTECTED]> wrote:
> On Wednesday 09 March 2005 1:17 am, Shiju Mathew wrote:
> > Hi,
> > When I connect the usb audio(CM108) to a U
I'm trying to sniff the firmware of a USB2 DVB-T receiver, using 2.6.10 and
vmware. I saw Greg Kroah-Hartman's article in Linux Journal, and tried to
use his snooping support. The device is working(slowly) in vmware.
Unfortunately, the syslog doesn't show the firmware. I can see that the
firmware i
I did not use the ezusb driver all that much. If I remember
correctly, the ezusb driver provide ioctl pretty straight forward.
It is similar enough to map to the usbdevfs.
You should read the documents or header file for the ezusb to
see what does the those ioctl do. e.g. If it is reading from a
b
What is the windows driver it is using? Unlike linux, windows
doesn't provide usbdevfs like API to send raw URB command from user
space. So I don't expect the windows DeviceIoControl call to have
1:1 mapping to usbdevfs(libusb). Chances are you need to know what
happens in the driver.
Chris
On W
Hi Alan & Dave,
> Just found out that we have a Adaptec-brand controller using a EHCI 1.0 NEC
> chip in one of the servers at work:
I've now bought an Adaptec AUA-3100. It uses a NEC D720101 which is EHCI 1.0
compliant. It looks much more solid than the cheap ALI and VIA cards I
previously trie
On Tuesday 08 March 2005 12:20 pm, Mark Hurenkamp wrote:
> > It'd be handy if you modified the HID driver to use the driver model
> > diagnostics ... you have several devices that could be triggering such
> > faults, and it's not clear which one(s) are doing this.
>
> Well, I can give it a try...
On Wednesday 09 March 2005 1:17 am, Shiju Mathew wrote:
> Hi,
> When I connect the usb audio(CM108) to a USB 2.0 hub which inturn is
> connected to the system root hub, the audio quality is very bad. I
> hear a audible buzz . But if I remove the ehci-hcd then the audo
> quality is perfectly fine. I
A Message From: linux-usb-devel@lists.sourceforge.net To: [EMAIL PROTECTED],
Subject: "Re: hi" was qualified as spam and held in quarantine on behalf of
[EMAIL PROTECTED]
Please contact the intended recipient if you want it released
---
SF em
Добрый_день!
Вы_хотите_прорекламировать_новую_услугу_или_продукт_Вашей_компании?
И_не_знаете_как_это_можно_сделать_качественно,_быстро__и_не_дорого?
Тогда_рассылки_по_электронной_почте_идеальный_для_Вас_выбор!
Все_вопросы_и_пожелания_можно_задавать_по_телефонам
/905/203'''9072,144'''5318
icq'''29
I used fxload to upload the firmware.
The piece of code I have is the interface that
communicates with the ezusb loaded with the firmware.
It's the windows source code. It uses the function
"DeviceIoControl" to communicate with the device.
I'd like to know how to replace this call with libusb
ones.
Hi,
When I connect the usb audio(CM108) to a USB 2.0 hub which inturn is
connected to the system root hub, the audio quality is very bad. I
hear a audible buzz . But if I remove the ehci-hcd then the audo
quality is perfectly fine. I read that the high speed isochronous
transfers through USB 2.0 hu
On Wed, Mar 09, 2005 at 08:45:58AM +0100, C?dric FINANCE wrote:
> Hello,
>
>
>I'm trying to write a driver for an usb device. It's a cartridge
> flasher based on a ezusb microcontroller. I talked with the developer
> and he gave me the firmware and a piece of code. I uploaded the firmware
I'm having problem with several embeded machines using USB2.0
Whenever I try to "stream" bulk URBs (that is, resubmit the URB immedaitely
from inside the irq handler), the kernel oopses somewhere in keventd.
I'm trying to record from my USB2.0 DVB-T receiver on an embeded device.
The receiver is Te
22 matches
Mail list logo
