All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jurriaan Kalkman" <Jurriaan.Kalkman@zrt.nl>
To: <parisc-linux@lists.parisc-linux.org>, <xam@student.cs.ucc.ie>
Subject: Betr.: [parisc-linux] C240: Graphics, 64bit kernel and more
Date: Mon, 12 Nov 2001 16:31:31 +0100	[thread overview]
Message-ID: <sbeffb9d.022@ms-zrt1> (raw)

>Hello,
>
>I'm going to buy a C240 (I already have a 730 (not here) and had a F10).
>It has 512MB and FX/2 24bit graphics. I think it's rather good supported
>by parisc-linux, am I right ?

yup.

>
>Before I actually buy the computer, I wanted to know whether STI
>and/or the framebuffer for a 64bit kernel is working.

sti is just working, IIRC

>
>Moreover I've read that UW-SCSI is not working yet.
>So is it working in FAST-SCSI (narrow) mode ?

there's nothing wrong with the UW-SCSI to my knowledge.

>
>Are you aware of any other gcc/binutils bugs or should
>gcc/binutils NOW create proper executables for pa2.0 and
>pa1.1 (including the old CPUs like 730's PCX-S CPU) ?

There are still bugs.

>
>does produce gcc rather good optimized code for parisc
>(compared to HP's cc, is there a significant performance difference) ?

in general, comparing gcc to a manufacturers compiler; there is
such a difference.

>
>I can imagine that the Linux/HPPA kernel is not very optimized yet
>(can't compare the speed on my 730 with HP/UX since I don't
>have the OS software anymore ...). Is the speed difference just a
>few percent or can you 'feel' it (mhh, fuzzy question) ?
>
I can only say that compiling a kernel on my C200 takes about 2 times
as long as on my alpha (21164, 500 Mhz, 2 Mb cache). I feel it should
be faster.

Good luck,
Jurriaan

                 reply	other threads:[~2001-11-12 15:44 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=sbeffb9d.022@ms-zrt1 \
    --to=jurriaan.kalkman@zrt.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 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.