From: Erik Steffl <steffl@bigfoot.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: ide <-> via VT82C693A/694x problems?
Date: Wed, 01 May 2002 02:01:34 -0700 [thread overview]
Message-ID: <3CCFAEEE.AE586B9A@bigfoot.com> (raw)
In-Reply-To: <Pine.LNX.4.10.10204301754310.2107-100000@master.linux-ide.org> <3CCF4BFD.6C7F67EB@bigfoot.com> <1020239797.10097.68.camel@nomade>
Xavier Bestel wrote:
>
> Le mer 01/05/2002 à 03:59, Erik Steffl a écrit :
> > the MB uses via chips so I included via82cxxx driver (as a module). is
> > that correct?
> >
> > however, I just checked and via82cxxx is NOT loaded. What do I need to
> > do to make ide driver is using via82cxxx module?
> >
> > I have ide driver compiled in (booting from ide hd), does via82cxxx
> > have to be compiled in?
>
> You mean the ide module is on the ide drive ? And you want it to be
> loaded before any ide access ?
ide is compiled in (not a module), via82cxxx is a module.
via82cxxx is never loaded - what do I need to do to actually use this
module? Most other modules are loaded either automatically or an alias
is needed, however I have no idea what to do to make kernel use
via82cxxx (would ide module use it?). I thought that as long as I
configure it in kernel make xconfig as a module it will be used, but
it's not loaded (so I guess it's not used).
I suspect that it might be the reason why my cd drive does not rip
audio cds...
erik
next prev parent reply other threads:[~2002-05-01 9:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-01 0:49 ide <-> via VT82C693A/694x problems? Erik Steffl
2002-05-01 0:56 ` Andre Hedrick
2002-05-01 1:59 ` Erik Steffl
2002-05-01 7:56 ` Xavier Bestel
2002-05-01 9:01 ` Erik Steffl [this message]
2002-05-01 17:42 ` Vojtech Pavlik
2002-05-01 19:33 ` Erik Steffl
2002-05-02 8:37 ` Vojtech Pavlik
2002-05-12 12:33 ` Erik Steffl
2002-05-01 16:58 ` Martin Dalecki
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=3CCFAEEE.AE586B9A@bigfoot.com \
--to=steffl@bigfoot.com \
--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 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.