All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alan Cox <alan@redhat.com>
To: Linux and Kernel Video <video4linux-list@redhat.com>
Cc: "'Alan Cox'" <alan@redhat.com>,
	Mauro Carvalho Chehab <mchehab@infradead.org>,
	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: Fri, 17 Mar 2006 15:02:30 -0500	[thread overview]
Message-ID: <20060317200230.GA13144@devserv.devel.redhat.com> (raw)
In-Reply-To: <820212CF2FD63647B52A8F64B35352B20B94229B@essomaexc1.essvote.com>

On Fri, Mar 17, 2006 at 09:59:44AM -0600, Ballentine, Casey wrote:
> Attached please find the output of "lspci -vvxxx" using the released 1.05
> BIOS and the 1.05 test BIOS on a VIA EPIA PD-10000 mainboard (CLE266
> northbridge and vt8235 southbridge).  Hopefully this will shed some light on
> what VIA is doing.  Let me know if I can provide more information.

Ok the changes in the PCI space are

82C586_1		:	0x70 was 0x22: now 0x42
8235	(South)		:	0x91 was 0x00 now 0x03
862X	(North)		:	0x61 was 2a now ea 0x62 was 00 now 03 0x68
				was 0xD1 now 0xCA 0x81 was 0x61 now 0x69


8235 0x91 is just general purpose timer control
82C586_1 0x70 is an IDE status bit

So the changes that matter are those (or some of those) on the 862X. Which is
the one bit I don't have docs on


       reply	other threads:[~2006-03-17 20:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <820212CF2FD63647B52A8F64B35352B20B94229B@essomaexc1.essvote.com>
2006-03-17 20:02 ` Alan Cox [this message]
     [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

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=20060317200230.GA13144@devserv.devel.redhat.com \
    --to=alan@redhat.com \
    --cc=bunk@stusta.de \
    --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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.