mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Roland Mas <roland.mas@free.fr>
To: linux-kernel@vger.kernel.org
Subject: Re: Drivers *dropped* between releases? (sis5513.c)
Date: Sun, 04 Apr 2004 17:51:37 +0200	[thread overview]
Message-ID: <871xn3hhbq.fsf@mirexpress.internal.placard.fr.eu.org> (raw)
In-Reply-To: <1GP0Q-6Fz-9@gated-at.bofh.it> (Lionel Bouton's message of "Sat, 03 Apr 2004 10:50:08 +0200")

Lionel Bouton, 2004-04-03 10:50:08 +0200 :

> Roland Mas wrote the following on 04/03/2004 10:19 AM :
>
>>[...]
>>  More relevant info (maybe): I got an old version of the Debian
>>installer, which uses an older kernel, and the process goes on
>>normally (well, it halts later because the built-in NIC has a stupid
>>MAC address, but that's another problem).
>
> If you can find the time, please check that this old installer
> doesn't use the sis5513 driver or DMA transfers. If it does both,
> I'd be really interested by the exact kernel version used. 

uname -a reports "2.4.22-1-386", although I suppose it's been patched
by the debian-installer team.  After hardware detection has run and
worked (as in, no hangs), sis5513 does indeed appear in lsmod, and
"dmesg | grep -i dma" tells me hda and hdc do use DMA.

> If it doesn't, you'd probably found yourself a workaround by
> disabling dma at boot time.

  I couldn't find out how to do that.  I tried booting with a long
"linux nodma hda=nodma hdc=nodma ide=nodma idebus=nodma" command-line,
but that didn't seem to change much.  I also tried disabling
everything that looked like DMA in the BIOS setup, to no avail.  dmesg
still tells me the kernel uses DMA (or maybe I don't understand what
dmesg tells me, which is of course entirely possible).

Roland.
-- 
Roland Mas

Late frost burns the bloom / Would a fool not let the belt / Restrain the body?
  -- in Good Omens (Terry Pratchett and Neil Gaiman)

       reply	other threads:[~2004-04-04 15:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1GOHw-6te-9@gated-at.bofh.it>
     [not found] ` <1GOHw-6te-11@gated-at.bofh.it>
     [not found]   ` <1GOHw-6te-7@gated-at.bofh.it>
     [not found]     ` <1GP0Q-6Fz-9@gated-at.bofh.it>
2004-04-04 15:51       ` Roland Mas [this message]
     [not found] <1GDM3-6G3-5@gated-at.bofh.it>
     [not found] ` <1GFEd-8b8-15@gated-at.bofh.it>
2004-04-03  8:19   ` Roland Mas
2004-04-03  8:40     ` Lionel Bouton
2004-04-02 20:37 Roland Mas
2004-04-02 22:39 ` Lionel Bouton

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=871xn3hhbq.fsf@mirexpress.internal.placard.fr.eu.org \
    --to=roland.mas@free.fr \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®