Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Matthew Wilcox <willy@debian.org>
To: James S <smithjames@comcast.net>
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] Printer Port & kernel stuff
Date: Tue, 5 Mar 2002 20:07:11 +0000	[thread overview]
Message-ID: <20020305200711.E30960@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <005101c1c480$ae437900$02c1a8c0@james.co.uk>; from smithjames@comcast.net on Tue, Mar 05, 2002 at 03:02:29PM -0500

On Tue, Mar 05, 2002 at 03:02:29PM -0500, James S wrote:
> Has nobody else had the same problem as me with the printer port ?
> 
> My 712/60 locks every time i send anything to the local printer.

Isn't this cured with Thomas Bogendoerfer's recent changes to make
parport_gsc & parport_pc work when compiled into the same kernel?

> while i'm at it - does anybody have a list of the options i should choose
> when i'm doing a make config for the kernel so i can get the right network
> stuff installed etc.

defconfig is pretty all-encompassing.  there's also the debian-configs
in the CVS tree.

> i need to recompile to include smbfs (which i think would be very handy if
> compiled into the kernel as standard)

last i heard it still wouldn't compile.  but maybe it got fixed and i
don't remember.

-- 
Revolutions do not require corporate support.

  parent reply	other threads:[~2002-03-05 20:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-05 20:02 [parisc-linux] Printer Port & kernel stuff James S
2002-03-05 20:05 ` Ralf Hildebrandt
2002-03-05 20:07 ` Matthew Wilcox [this message]
2002-03-05 20:12   ` James S
2002-03-08  0:33     ` [parisc-linux] traps in whiptail with apt-get upgrade Peter Weilbacher
2002-03-06  5:58   ` [parisc-linux] Printer Port & kernel stuff Carlos O'Donell Jr.
2002-03-07  3:44   ` James S

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=20020305200711.E30960@parcelfarce.linux.theplanet.co.uk \
    --to=willy@debian.org \
    --cc=parisc-linux@lists.parisc-linux.org \
    --cc=smithjames@comcast.net \
    /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