All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: Pavel Machek <pavel@suse.cz>
Cc: Ingo Molnar <mingo@elte.hu>,
	"Maciej W. Rozycki" <macro@linux-mips.org>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Peter Zijlstra <peterz@infradead.org>,
	Jiri Kosina <jkosina@suse.cz>, Adam Osuchowski <adwol@zonk.pl>,
	linux-kernel@vger.kernel.org, Nick Piggin <npiggin@suse.de>,
	Thomas Gleixner <tglx@linutronix.de>,
	"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: Is 386 processor still supported?
Date: Fri, 16 Jan 2009 11:13:19 +0100	[thread overview]
Message-ID: <20090116101319.GT11087@lug-owl.de> (raw)
In-Reply-To: <20090116090002.GD4795@atrey.karlin.mff.cuni.cz>

[-- Attachment #1: Type: text/plain, Size: 674 bytes --]

On Fri, 2009-01-16 10:00:02 +0100, Pavel Machek <pavel@suse.cz> wrote:
> > patches are welcome ...
> 
> Hehe, I guess the only long-term solution is to get shiny old 386 as a
> part of Ingo's test farm ;-).

:-D  I'm currently cleaning up the flat, 'll try to dig out the old
patch tonight. Maybe I can play with it a bit on my original i386
hardware. (I've already tested it, it still powers on and boots up
that ancient debian version. Using a 20GB (right, gigabytes) HDD.)

MfG, JBG

-- 
      Jan-Benedict Glaw      jbglaw@lug-owl.de              +49-172-7608481
Signature of:                http://catb.org/~esr/faqs/smart-questions.html
the second  :

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2009-01-16 10:13 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-08 12:03 Is 386 processor still supported? Adam Osuchowski
2009-01-08 13:05 ` Jiri Kosina
2009-01-08 13:24   ` Cyrill Gorcunov
2009-01-08 13:48     ` Jiri Kosina
2009-01-08 14:13   ` Peter Zijlstra
2009-01-08 14:21     ` Jiri Kosina
2009-01-08 14:27       ` Peter Zijlstra
2009-01-08 15:04         ` Alan Cox
2009-01-08 15:10           ` Ingo Molnar
2009-01-13  1:06             ` Maciej W. Rozycki
2009-01-15 12:36               ` Jan-Benedict Glaw
2009-01-15 13:22                 ` Maciej W. Rozycki
2009-01-15 13:32                   ` Alan Cox
2009-01-15 14:15                     ` Maciej W. Rozycki
2009-01-15 14:17                       ` Ingo Molnar
2009-01-16  9:00                         ` Pavel Machek
2009-01-16 10:13                           ` Jan-Benedict Glaw [this message]
2009-01-16 11:18                           ` Andrey Panin
2009-01-16 13:46                           ` Ingo Molnar
2009-01-16 18:17                           ` H. Peter Anvin
2009-01-15 14:20                       ` Jan-Benedict Glaw
2009-01-15 14:37                         ` Bastien ROUCARIES
2009-01-15 14:25                       ` Alan Cox
2009-01-15 14:44                         ` Maciej W. Rozycki
2009-01-15 20:11                           ` H. Peter Anvin
2009-01-15 14:46                     ` Jan-Benedict Glaw
2009-01-08 16:45         ` Sam Ravnborg
2009-01-08 16:27   ` Andi Kleen

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=20090116101319.GT11087@lug-owl.de \
    --to=jbglaw@lug-owl.de \
    --cc=adwol@zonk.pl \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=hpa@zytor.com \
    --cc=jkosina@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=macro@linux-mips.org \
    --cc=mingo@elte.hu \
    --cc=npiggin@suse.de \
    --cc=pavel@suse.cz \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    /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.