$B%5%$%H1?1D$H?=$7$^$9!#(B
(B
$B$3$N%a!<%k$O!"(BWEB$B>e$G%5%$%H1?1D$5$l$F$$$kJ}$K%"%/%;%9%"%C%W!JL5NA!K$N(B
$B$*CN$i$;%a!<%k$rG[?.$5$;$FD:$$$F$*$j$^$9!#(B
(B
$B"(!ZL$>5G'![$N0Y!"I,MW$N$J$$>l9g$dl9g$O(B
(B[EMAIL PROTECTED]"$*e0LI=<($5$l!"8=:_$G$O#2#0K|%"%/%;%9$r>e2s(B
$B$k$[$I$N?M5$
On Tuesday 28 December 2004 9:26 pm, Garth Kay-Hards wrote:
> However, with all the development on Linux why has the ease of plug and play
> not kept up with Windows? Is it because device manufactures only support
> Windows? Or mostly.
That's part of it.
Another part of it is that the UNIX commu
Greg and company,
As some of you probably know, I do the support for the sq905 cameras in
libgphoto2.
Just after Christmas, someone reported a new sq905 camera, saying that it
did not work. The log file showed the problem was that data sent from the
camera on the bulk pipe seems to get dropped:
Hi,
I use FC2 and kernel is 2.6.8.1.
I want to send 3 extra self-defined UFI command to USB memory stick before it
send the normal command such as INQUIRY, etc.(these extra command used to
unlock the secure USB stick!)
I read the Mass storage device driver code and found that such command are
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
David Brownell wrote:
| It's something wierd that started a while back, and so far
| it doesn't make sense to me. But see below, and please
| try the patch I've attached. If it fails, please send
| the full CONFIG_USB_DEBUG output showing the error (a
Hi!
> > Okay, it is probably different problem (and looks like usb
> > problem). It worked ok in 2.6.9, right?
>
> I don't know. This laptop is quite new.
> Noapic doesn't work.
Okay, it probably never worked before. I'm happy that it at least
works after unplug/replug :-). Probably better suspe
Am Dienstag, 4. Januar 2005 00:23 schrieb Pavel Machek:
> Hi!
>
> > > > with 2.6.10 (i386/UP/UHCI)
> > > > :00:1d.0 USB Controller: Intel Corp. 82801DB USB (Hub #1) (rev 03)
> > > > :00:1d.1 USB Controller: Intel Corp. 82801DB USB (Hub #2) (rev 03)
> > > > :00:1d.2 USB Controller: Inte
Hi!
> > > with 2.6.10 (i386/UP/UHCI)
> > > :00:1d.0 USB Controller: Intel Corp. 82801DB USB (Hub #1) (rev 03)
> > > :00:1d.1 USB Controller: Intel Corp. 82801DB USB (Hub #2) (rev 03)
> > > :00:1d.2 USB Controller: Intel Corp. 82801DB USB (Hub #3) (rev 03)
> > > :00:1d.7 USB Control
Am Montag, 3. Januar 2005 23:36 schrieb Pavel Machek:
> Hi!
>
> > with 2.6.10 (i386/UP/UHCI)
> > :00:1d.0 USB Controller: Intel Corp. 82801DB USB (Hub #1) (rev 03)
> > :00:1d.1 USB Controller: Intel Corp. 82801DB USB (Hub #2) (rev 03)
> > :00:1d.2 USB Controller: Intel Corp. 82801DB US
On Sunday 02 January 2005 1:16 pm, Thomas Brinker wrote:
> Hi!
>
> Am Samstag, 1. Januar 2005 18:18 schrieb David Brownell:
> > What sort of details are you looking for?
>
> I'm looking for some general information about what you have to do in order
> to
> implement some udc-drivers. The exist
On Llu, 2005-01-03 at 22:05, Alan Stern wrote:
> On Mon, 3 Jan 2005, Alan Cox wrote:
> Alan, I respect your judgement and your advice. If after looking more
> closely at this you still think the code should be changed to use barriers
> instead, I will do it.
>
> But first you should read my rep
Hi!
> with 2.6.10 (i386/UP/UHCI)
> :00:1d.0 USB Controller: Intel Corp. 82801DB USB (Hub #1) (rev 03)
> :00:1d.1 USB Controller: Intel Corp. 82801DB USB (Hub #2) (rev 03)
> :00:1d.2 USB Controller: Intel Corp. 82801DB USB (Hub #3) (rev 03)
> :00:1d.7 USB Controller: Intel Corp. 828
Hi,
with 2.6.10 (i386/UP/UHCI)
:00:1d.0 USB Controller: Intel Corp. 82801DB USB (Hub #1) (rev 03)
:00:1d.1 USB Controller: Intel Corp. 82801DB USB (Hub #2) (rev 03)
:00:1d.2 USB Controller: Intel Corp. 82801DB USB (Hub #3) (rev 03)
:00:1d.7 USB Controller: Intel Corp. 82801DB USB2
On Monday 03 January 2005 1:06 pm, Alan Cox wrote:
> > As the maintainer, I decided to go
> > in favor of simplicity and ease-of-maintenance.
>
> Thats unfortunate because we know from years of history its always been
> the wrong decision, that older gcc gets volatile wrong and that
> process
On Mon, 3 Jan 2005 17:05:25 -0500 (EST), Alan Stern <[EMAIL PROTECTED]> wrote:
> But first you should read my reply to Pete, and you should see how the
> driver is affected. You will be hard-pressed to find any spots where the
> "volatile" causes abominable code generation.
I saw your reply, a
On Monday 03 January 2005 12:49 pm, David Brownell wrote:
> It's something wierd that started a while back, and so far
> it doesn't make sense to me. But see below, and please
> try the patch I've attached.
And it _still_ doesn't make sense to me -- why should any
chip issue bogus "fatal" error
On Llu, 2005-01-03 at 19:50, Alan Stern wrote:
> Going in and inserting barriers by hand is a painstaking and
> error-prone process, particularly when the code changes in the
> future. By adding a single "volatile", I can make the compiler
> do all that work for me, with no
On Mon, 3 Jan 2005, Alan Cox wrote:
> On Llu, 2005-01-03 at 18:31, Pete Zaitcev wrote:
> > Fist is SMP: volatile does nothing to help serialize accesses, although
> > I can see that in perhaps in this case it's not an issue. The second
> > is portability: on a few CPUs special instructions are nec
On Llu, 2005-01-03 at 18:31, Pete Zaitcev wrote:
> Fist is SMP: volatile does nothing to help serialize accesses, although
> I can see that in perhaps in this case it's not an issue. The second
> is portability: on a few CPUs special instructions are necessary for
> serializations, which are provid
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Pedro Venda wrote:
| hi everyone,
|
| just subscribed.
|
| I'm using an ACER travelmate 4001WLMi and someone showed me that it has
| some
| problems with the ehci usb driver.
|
| without debug, i get the following:
|
| Dec 20 00:41:04 archon ehci_hcd 00
It's something wierd that started a while back, and so far
it doesn't make sense to me. But see below, and please
try the patch I've attached. If it fails, please send
the full CONFIG_USB_DEBUG output showing the error (as
below) and contents of /sys/class/usb_host/usb4/registers
after the fault.
On Mon, 3 Jan 2005, Pete Zaitcev wrote:
> This is not a good idea, at least not typically. This was extensively
> discussed before, and although I cannot repeat all arguments precisely,
> I remember that I found them convincing. It boils down to two things.
> Fist is SMP: volatile does nothing to
On Monday 03 January 2005 9:26 am, Olav Kongas wrote:
> Hi,
>
> Here comes a new isp116x driver. I took David Brownell's
> recently updated sl811 driver and ported it to isp116x
> chips. It is considerably smaller and simpler than other
> isp116x drivers for 2.6 kernel posted to this
> list recent
On Mon, 3 Jan 2005 11:02:22 -0500 (EST), Alan Stern <[EMAIL PROTECTED]> wrote:
> This patch adds "volatile" to a couple of declarations for fields in the
> UHCI driver that are susceptible to outside change by DMA. Without this
> or some similar approach to defeat gcc's optimizer, the compiler
Greg:
This patch adds "volatile" to a couple of declarations for fields in the
UHCI driver that are susceptible to outside change by DMA. Without this
or some similar approach to defeat gcc's optimizer, the compiler will
generate incorrect references to these fields.
Please apply.
Alan Stern
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hi everyone,
just subscribed.
I'm using an ACER travelmate 4001WLMi and someone showed me that it has some
problems with the ehci usb driver.
without debug, i get the following:
Dec 20 00:41:04 archon ehci_hcd :00:1d.7: fatal error
Dec 20 00:41:04 a
On Thu, Dec 16, Takashi Iwai wrote:
> At Tue, 14 Dec 2004 22:11:16 +0100,
> Olaf Hering wrote:
> >
> >
> > Got a soundblaster live 24bit today, it works ok with 2.6.10-rc3.
> >
> > I got this crash while playing a wav file in a loop.
> > while true;do aplay /usr/share/sounds/alsa/test.wav;done
Międzynarodowe Centrum Informacyjno - Konsultingowe "ICIC", Kijów,
Ukraina.
www.seminar-ua.com
Serdecznie zaprasza na
> XI Międzynarodową polsko - ukraińsko - rosyjską konferencję
28 matches
Mail list logo
