From: Mauro Carvalho Chehab <mchehab@infradead.org>
To: Alan Cox <alan@redhat.com>
Cc: Linux and Kernel Video <video4linux-list@redhat.com>,
linux-usb-devel@lists.sourceforge.net,
usb-storage@lists.one-eyed-alien.net,
linux-kernel@vger.kernel.org, Adrian Bunk <bunk@stusta.de>,
v4l-dvb-maintainer@linuxtv.org, mdharm-usb@one-eyed-alien.net
Subject: Re: [usb-storage] Re: [v4l-dvb-maintainer] 2.6.16-rc: saa7134 + u sb-storage = freeze
Date: Thu, 16 Mar 2006 16:55:11 -0300 [thread overview]
Message-ID: <1142538911.4666.69.camel@praia> (raw)
In-Reply-To: <20060315234421.GB4414@devserv.devel.redhat.com>
Em Qua, 2006-03-15 às 18:44 -0500, Alan Cox escreveu:
> On Wed, Mar 15, 2006 at 03:24:40PM -0600, Ballentine, Casey wrote:
> > I would bet we could add the vt8235 to the list of broken chipsets
> > as well, if it's not already there. My company has completely
>
> "Works for me" 8)
On overlay mode? Weird!
>
> A lot of this is BIOS dependant and if we can isolate cases where one
> BIOS works and another doesn't an lspci -vvxxx would be helpful so we
> can look for chipset pokery
If bios can safely configure PCI2PCI data transfers, maybe we can
identify what bios do different and include at kernel. It is really bad
to have OOPS or data corruption if using some bad BIOS. IMHO, if we
can't safely have a way to tune pci2pci stuff at chipset, it is better
to include the hack and let the no_overlay parameter (or maybe instead a
quirk parameter at pci quirks.c) to allow user to force it.
>
>
> _______________________________________________
> v4l-dvb-maintainer mailing list
> v4l-dvb-maintainer@linuxtv.org
> http://www.linuxtv.org/cgi-bin/mailman/listinfo/v4l-dvb-maintainer
Cheers,
Mauro.
next prev parent reply other threads:[~2006-03-16 19:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <820212CF2FD63647B52A8F64B35352B20B942298@essomaexc1.essvote.com>
2006-03-15 23:44 ` [usb-storage] Re: [v4l-dvb-maintainer] 2.6.16-rc: saa7134 + u sb-storage = freeze Alan Cox
2006-03-15 23:49 ` Adrian Bunk
2006-05-17 14:13 ` Alan Cox
2006-03-16 19:55 ` Mauro Carvalho Chehab [this message]
2006-03-16 21:27 ` Alan Cox
2006-03-16 15:41 ` [linux-usb-devel] " Alan Stern
2006-03-20 22:09 ` thomas schorpp
2006-03-21 14:59 ` Mauro Carvalho Chehab
2006-03-22 23:49 ` thomas schorpp
[not found] <820212CF2FD63647B52A8F64B35352B20B94229B@essomaexc1.essvote.com>
2006-03-17 20:02 ` Alan Cox
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1142538911.4666.69.camel@praia \
--to=mchehab@infradead.org \
--cc=alan@redhat.com \
--cc=bunk@stusta.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=mdharm-usb@one-eyed-alien.net \
--cc=usb-storage@lists.one-eyed-alien.net \
--cc=v4l-dvb-maintainer@linuxtv.org \
--cc=video4linux-list@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox