From: "\"Beerse, Corné\"" <c.beerse@torex-hiscom.nl>
To: "'Martin-Éric Racine'" <q-funk@pp.fishpool.fi>
Cc: parisc-linux <parisc-linux@parisc-linux.org>
Subject: RE: [parisc-linux] hardware features of 712-60 ?
Date: Fri, 11 Oct 2002 11:47:40 +0200 [thread overview]
Message-ID: <02Oct11.120046cest.119067@ns.hiscom.nl> (raw)
[-- Attachment #1: Type: text/plain, Size: 1917 bytes --]
> -----Original Message-----
> From: Martin-Éric Racine [mailto:q-funk@pp.fishpool.fi]
> On Fri, 11 Oct 2002, "Beerse, Corné" wrote:
>
> > > At this point, I apt-got kernel-source-2.4.19-hppa and
> > > unpacked it, and already
> > > selected the 7100LC/7300LC CPU option. What else? Has
> > > anybody compiled a FAQ
> > > on parisc-linux that provides .config files optimized for
> > > each PA-RISC hardware
> > > or, alternately, a checklist of hardware one finds in product
> > > xxx, referenced by
> > > Linux kernel feature or module name?
> >
> > Have you checked the hardware database on the website?
> > (http://www.parisc-linux.org/) That gives an overview on
> what whas in the
> > origional box.
>
> http://hwdb.parisc-linux.org/view.php3?type=machine&name=712%2F60
>
> That page could have been written in Chinese, it would have
> been equally clear.
>
> I guess I'm just used to PC hardware, where kernel compiling
> simply means "if
> you have graphics card XXX select the driver with the same
> name". I've yet to
Which most times results in a lot of variants for the same card (since
manufacturers update hardware without updating the type info) and lots of
names for stuf using the same chipset. I think it is just what you are used
ot. both have their pro-s and con-s.
> find that simplicity in HP hardware, probably because
> everything is done via
> custom chips that combine several functions, and it is not
> clear to me which
> chip does what, as every line in that page starts with Gecko.
I think this Gecko is the name of the development of the machine. I think
(never looked) the terms can be found in the source too (if required). Its
just a little more pronouncable than 9000/712/60... You're working on
workstations. If you look at servers (9000/800 range) then it is an even
stranger view at first sight.
CBee
[-- Attachment #2: Type: text/html, Size: 3522 bytes --]
next reply other threads:[~2002-10-11 9:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-11 9:47 "Beerse, Corné" [this message]
[not found] <02Oct11.113022cest.119055@ns.hiscom.nl>
2002-10-11 9:34 ` [parisc-linux] hardware features of 712-60 ? Martin-Éric Racine
2002-10-11 9:40 ` Patrick Caulfield
2002-10-11 11:28 ` Thibaut VARENE
2002-10-11 12:22 ` Martin-Éric Racine
2002-10-11 12:33 ` Ralf Hildebrandt
2002-10-11 12:54 ` Matthew Wilcox
2002-10-11 12:59 ` Martin-Éric Racine
2002-10-11 13:24 ` Thibaut VARENE
2002-10-12 14:08 ` Yves Bodack
-- strict thread matches above, loose matches on Subject: below --
2002-10-11 9:03 Martin-Éric Racine
2002-10-12 9:18 ` kenneth westelinck
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=02Oct11.120046cest.119067@ns.hiscom.nl \
--to=c.beerse@torex-hiscom.nl \
--cc=parisc-linux@parisc-linux.org \
--cc=q-funk@pp.fishpool.fi \
/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