From: Jurriaan on Alpha <thunder7@xs4all.nl>
To: Markus Grabert <xam@student.cs.ucc.ie>
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] State of official Linux kernel
Date: Mon, 19 Nov 2001 21:13:49 +0100 [thread overview]
Message-ID: <20011119211349.A19479@alpha.of.nowhere> (raw)
In-Reply-To: <Pine.OSF.4.41.0111191911120.11606-100000@student.cs.ucc.ie>
On Mon, Nov 19, 2001 at 07:40:28PM +0000, Markus Grabert wrote:
> Hi,
>
> I'm just curious what the state of the PA-RISC support of the
> official linux kernel is (2.4.14 from kernel.org).
>
> IMHO I assume that the latest Linux/PA-RISC progress didn't and won't
> make it in the official linux kernel tree (at least not soon), am I right ?
> (I don't see any hppa changes in the kernel-Changelogs at all)
Not while there are multiple changes per day - anyone with a parisc
machine tracks the parisc-kernel anyway, so what would be the point?
>
> Probably due to the fact that Linux/PA-RISC is still somewhat
> experimental and probably some design issues are not fixed yet.
> Are there any plans to integrate the lastest stuff into the
> linux main tree (soon) ?
I gather there's more use in fixing bugs than merging. Also see above.
>
> What about gcc, gdb, glibc and binutils ? How long do you think does it
> take to get the current fixes/patches into a release ?
There's some tough bugs at the moment, and I hope that after those are
squashed our hard-working developers will have the time to concentrate
on the kernel, with a relatively stable parisc development userland.
>
> AFAIK RedHat/Cygnus supports/maintains gcc, gdb, glibc and binutils.
> Are there (usually) any problems to get the patches/fixes (of gcc, gdb,
> ...) into a official release ? How good is the cooperation with the main
> developers of these tools/libraries ? RedHat doesn't seem to be interested
> in an Linux/PA-RISC port and debian is something like a competitor ...
>
You can't be serious. Debian/parisc is no competitior of RedHat. I
assume there would be no problem getting fixes in if they are the right
fixes. At this moment, I haven't seen a clear email saying: 'all bugs in
the development tools have been found, go forth and apt-get update!'.
Good luck,
Jurriaan
--
IBM: I'm Beyond Mistakes
GNU/Linux 2.4.15-pre6 on Debian/Alpha 64-bits 988 bogomips load:0.15 0.53 0.61
prev parent reply other threads:[~2001-11-19 20:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-19 19:40 [parisc-linux] State of official Linux kernel Markus Grabert
2001-11-19 20:03 ` Randolph Chung
2001-11-19 20:13 ` Jurriaan on Alpha [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=20011119211349.A19479@alpha.of.nowhere \
--to=thunder7@xs4all.nl \
--cc=parisc-linux@lists.parisc-linux.org \
--cc=xam@student.cs.ucc.ie \
/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