public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: thomas schorpp <t.schorpp@gmx.de>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: "Ballentine, Casey" <crballentine@essvote.com>,
	video4linux-list@redhat.com,
	linux-usb-devel@lists.sourceforge.net,
	usb-storage@lists.one-eyed-alien.net,
	v4l-dvb-maintainer@linuxtv.org,
	"'Mauro Carvalho Chehab'" <mchehab@infradead.org>,
	mdharm-usb@one-eyed-alien.net, linux-kernel@vger.kernel.org,
	Adrian Bunk <bunk@stusta.de>
Subject: Re: [linux-usb-devel] RE: [usb-storage] Re: [v4l-dvb-maintainer] 2.6.16-rc: saa7134 + u sb-storage = freeze
Date: Mon, 20 Mar 2006 23:09:34 +0100	[thread overview]
Message-ID: <441F281E.5060405@gmx.de> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0603161039410.5253-100000@iolanthe.rowland.org>

Alan Stern wrote:
> On Wed, 15 Mar 2006, Ballentine, Casey wrote:
> 
> 
>>Mauro,
>>
>>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 
>>disabled DMA in the 2.6.13.4 kernel we're running on an 
>>EPIA PD-10000 board due to lockupslike these.  We came across 
>>a thread on the via arena website while researching possible 
>>problems on the VIA boards:
>>
>>http://forums.viaarena.com/messageview.aspx?catid=28&threadid=60131&STARTPAG
>>E=1&FTVAR_FORUMVIEWTMP=Linear
> 
> 
> Here's another interesting link from VIA's site.  They claim to have fixed 
> the DMA problem (for some boards, anyway):
> 
> http://forums.viaarena.com/messageview.aspx?catid=28&threadid=67386&enterthread=y
> 
> Alan Stern
> 
> _______________________________________________
> Usb-storage mailing list
> Usb-storage@lists.one-eyed-alien.net
> https://lists.one-eyed-alien.net/mailman/listinfo/usb-storage
> 
> 

what DMA problem? ive always used via chipsets with usb. now the 8237. 

the via pci-busmaster dma hangs the system? try setting pci latency to 64.
most bioses initialize with 32. this had been a known problem, for me too.
this has been left out of the discussion at via forums.

and what knows a usb controller about MPEG? thats another layer.

so a bios fixes this and other os have no problem with this, 
so its fixable by software. then do it now, pls.

and stop this "blacklisting habit", all these nowadays chips are designed-to-cost 
"consumer crap" somewhow.
or do you want linux-usb to be blacklisted as "broken" by the manufacturers blacklists? ;)


y
tom


  reply	other threads:[~2006-03-20 22:10 UTC|newest]

Thread overview: 9+ 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
2006-03-16 21:27     ` Alan Cox
2006-03-16 15:41 ` [linux-usb-devel] " Alan Stern
2006-03-20 22:09   ` thomas schorpp [this message]
2006-03-21 14:59     ` Mauro Carvalho Chehab
2006-03-22 23:49       ` thomas schorpp

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=441F281E.5060405@gmx.de \
    --to=t.schorpp@gmx.de \
    --cc=bunk@stusta.de \
    --cc=crballentine@essvote.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    --cc=mchehab@infradead.org \
    --cc=mdharm-usb@one-eyed-alien.net \
    --cc=stern@rowland.harvard.edu \
    --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