The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: "Nick Long" <nicklong@home.com>
To: "Geert Uytterhoeven" <geert@linux-m68k.org>
Cc: "kernel" <linux-kernel@vger.kernel.org>,
	"Tim Moore" <timothymoore@bigfoot.com>
Subject: Re: ncr53c8xx - DAT detection problem - 2.2.14-5
Date: Fri, 11 May 2001 21:16:21 -0700	[thread overview]
Message-ID: <0c5201c0da9a$4d736200$7dad0f18@Nick> (raw)
In-Reply-To: <Pine.LNX.4.05.10105110944520.1624-100000@callisto.of.borg>

Geert,  I have "CONFIG_CHR_DEV_ST=y" in my "/usr/src/linux/.config" file.
Any ideas?

----- Original Message -----
From: "Geert Uytterhoeven" <geert@linux-m68k.org>
To: <nicklong@home.com>
Cc: "kernel" <linux-kernel@vger.kernel.org>
Sent: Friday, May 11, 2001 12:45 AM
Subject: Re: ncr53c8xx - DAT detection problem - 2.2.14-5


> On Thu, 10 May 2001, Tim Moore wrote:
> > Any clues as to why /dev/st0 is never initialized for DAT tape?  Please
cc nicklong@home.com if more
> > info is needed.
>
> Make sure CONFIG_CHR_DEV_ST=[ym]
>
> Gr{oetje,eeting}s,
>
> Geert
>
> --
> Geert Uytterhoeven -- There's lots of Linux beyond ia32 --
geert@linux-m68k.org
>
> In personal conversations with technical people, I call myself a hacker.
But
> when I'm talking to journalists I just say "programmer" or something like
that.
>     -- Linus Torvalds
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/


      reply	other threads:[~2001-05-12  3:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-11  2:32 ncr53c8xx - DAT detection problem - 2.2.14-5 Tim Moore
2001-05-11  7:45 ` Geert Uytterhoeven
2001-05-12  4:16   ` Nick Long [this message]

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='0c5201c0da9a$4d736200$7dad0f18@Nick' \
    --to=nicklong@home.com \
    --cc=geert@linux-m68k.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=timothymoore@bigfoot.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