public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Ivica Ico Bukvic <ico@fuse.net>
Cc: daniel.ritz@gmx.ch, "'Tim Blechmann'" <TimBlechmann@gmx.net>,
	"'Thomas Charbonnel'" <thomas@undata.org>,
	ccheney@debian.org, linux-pcmcia@lists.infradead.org,
	alsa-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [linux-audio-user] snd-hdsp+cardbus+M6807 notebook=distortion -- FIXED!
Date: Mon, 12 Apr 2004 15:53:36 +0100	[thread overview]
Message-ID: <20040412155336.B12980@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20040412144103.PIXB8029.smtp1.fuse.net@64BitBadass>; from ico@fuse.net on Mon, Apr 12, 2004 at 10:40:59AM -0400

On Mon, Apr 12, 2004 at 10:40:59AM -0400, Ivica Ico Bukvic wrote:
> Sorry :-) Mandrake Community 10.0 using the 2.6.3 kernel with a patch to fix
> the freezing when probing for the pcmcia card on this particular notebook
> (see: http://www.muru.com/linux/amd64/).

Pavel's fix isn't really a fix, it's more a work-around.  If we keep
increasing PCIBIOS_MIN_CARDBUS_IO until we hit 0xffff, everyones
system stops working.

The problem there will be that there's some IO registers between 0x4000
and 0x5000 which the BIOS wants access to, but the kernel didn't know
that they existed.

In any case, 2.6.3 does not contain the patches for CB1410, so chances
are that your problem is already half solved in 2.6.5.

Ok, so the action plan is:

- set 0xc9 to 0x04 for CB1410 (and others?)
- find a reasonable solution to the latency timer, maybe just setting it
  to 0xff when we detect the bridge.

-- 
Russell King
 Linux kernel    2.6 ARM Linux   - http://www.arm.linux.org.uk/
 maintainer of:  2.6 PCMCIA      - http://pcmcia.arm.linux.org.uk/
                 2.6 Serial core

  reply	other threads:[~2004-04-12 14:53 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-10  1:47 [linux-audio-user] snd-hdsp+cardbus+M6807 notebook=distortion -- First good news Daniel Ritz
2004-04-10  3:30 ` Ivica Ico Bukvic
2004-04-11 13:25   ` Russell King
2004-04-11 16:08     ` Tim Blechmann
2004-04-11 23:45       ` Daniel Ritz
2004-04-12  1:39         ` [linux-audio-user] snd-hdsp+cardbus+M6807 notebook=distortion -- FIXED! Ivica Ico Bukvic
2004-04-12  7:28           ` Russell King
2004-04-12  9:08             ` David Hinds
2004-04-12  9:27               ` Russell King
2004-04-12 14:40             ` Ivica Ico Bukvic
2004-04-12 14:53               ` Russell King [this message]
2004-04-12 15:31                 ` Daniel Ritz
2004-04-12 15:38                   ` Russell King
2004-04-12 18:03                     ` Daniel Ritz
2004-04-14 13:41                     ` Tim Blechmann
2004-04-12 22:06               ` Tim Blechmann
2004-04-12 11:02           ` Tim Blechmann
2004-04-12 10:39             ` Russell King
2004-04-12 12:09               ` Tim Blechmann
2004-04-12 15:19           ` Daniel Ritz

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=20040412155336.B12980@flint.arm.linux.org.uk \
    --to=rmk+lkml@arm.linux.org.uk \
    --cc=TimBlechmann@gmx.net \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=ccheney@debian.org \
    --cc=daniel.ritz@gmx.ch \
    --cc=ico@fuse.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pcmcia@lists.infradead.org \
    --cc=thomas@undata.org \
    /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