All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Linux Kernel Development <linux-kernel@vger.kernel.org>
Subject: Re: [2.6 patch] remove support for gcc < 3.2
Date: Fri, 12 Aug 2005 14:29:35 +0200	[thread overview]
Message-ID: <20050812122935.GA25012@lug-owl.de> (raw)
In-Reply-To: <Pine.LNX.4.62.0508120938560.18366@numbat.sonytel.be>

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

On Fri, 2005-08-12 09:40:18 +0200, Geert Uytterhoeven <geert@linux-m68k.org> wrote:
> On Thu, 4 Aug 2005, Jan-Benedict Glaw wrote:
> > -sh-3.00# cat cpuinfo
> > cpu             : VAX
> > cpu type        : KA43
> > cpu sid         : 0x0b000006
> > cpu sidex       : 0x04010002
> > page size       : 4096
> > BogoMIPS        : 10.08
> > -sh-3.00# cat version
> > Linux version 2.6.12 (jbglaw@d2) (gcc version 4.1.0 20050803 (experimental)) #2 Wed Aug 3 23:42:11 CEST 2005
> 
> Any change we will see this code in mainline?

That's the plan. We haven't publically talked about it yet, but we'd
probably like to present the code for review once we

	- have enough hardware supported. At least local SCSI drivers
	  for the most common machines should be available, as well as
	  network drivers. That's not yet the case.

	- have userspace working again. Currently, a very old gcc is
	  used. I'm working on uClibc (and thereafter GNU libc) in
	  conjunction with gcc-HEAD as time allows.

So yes, we want to show off the code, but we don't want to do that
publically and right now. There are still to many places where the code
needs some tidy-up (and be it whitespace and comment fixes), but
everybody is welcome to peek at our CVS repo
(http://sourceforge.net/cvs/?group_id=2626) or to join the mailing list
(at http://www.pergamentum.com/mailman/listinfo/linux-vax).

So if *you* are looking for some beginner's task to start with kernel
development, here you go! Oh, and SMP fun will hopefully start soon. A
machine is on the way and I hope it'll survive shipping :-)

VAX is also an interesting platform because it's another platform
offering TurboChannel slots. So if you're interested in those old Alphas
or DECstations, VAX is for you, too.

MfG, JBG

-- 
Jan-Benedict Glaw       jbglaw@lug-owl.de    . +49-172-7608481             _ O _
"Eine Freie Meinung in  einem Freien Kopf    | Gegen Zensur | Gegen Krieg  _ _ O
 fuer einen Freien Staat voll Freier Bürger" | im Internet! |   im Irak!   O O O
ret = do_actions((curr | FREE_SPEECH) & ~(NEW_COPYRIGHT_LAW | DRM | TCPA));

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

      parent reply	other threads:[~2005-08-12 12:29 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-31 22:26 [2.6 patch] remove support for gcc < 3.2 Adrian Bunk
2005-07-31 22:36 ` David S. Miller
2005-07-31 23:08   ` Nigel Cunningham
2005-08-07 16:25   ` Denis Vlasenko
2005-08-10 19:40   ` Bill Davidsen
2005-08-11  0:02     ` Joe
2005-08-11  0:05       ` David S. Miller
2005-08-13  3:27       ` Bill Davidsen
2005-08-01  3:01 ` [2.6 patch] " Kurt Wall
2005-08-02  5:37   ` Willy Tarreau
2005-08-01  4:27 ` Miles Bader
2005-08-02 21:46 ` Jan-Benedict Glaw
2005-08-03  2:08 ` Gustavo Guillermo Pérez
2005-08-04  0:53   ` Mathieu Chouquet-Stringer
2005-08-04 20:34     ` networking problems when using gcc 4.0.1 Adrian Bunk
2005-08-04  1:34 ` [2.6 patch] remove support for gcc < 3.2 Dave Airlie
2005-08-04  6:54   ` Jan-Benedict Glaw
2005-08-04 20:38     ` Adrian Bunk
2005-08-05 21:14       ` Jan-Benedict Glaw
2005-08-05 21:30         ` Martin Drab
2005-08-05 21:37           ` Jan-Benedict Glaw
2005-08-13  9:21       ` Jan-Benedict Glaw
2005-08-12  7:40     ` Geert Uytterhoeven
2005-08-12 10:40       ` Maciej W. Rozycki
2005-08-12 12:29       ` Jan-Benedict Glaw [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=20050812122935.GA25012@lug-owl.de \
    --to=jbglaw@lug-owl.de \
    --cc=geert@linux-m68k.org \
    --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.