All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Marteau <marteaut@esiee.fr>
To: Grant Grundler <grundler@puffin.external.hp.com>
Cc: Bjorn Helgaas <bjorn_helgaas@hp.com>,
	"parisc-linux@parisc-linux.org" <parisc-linux@parisc-linux.org>
Subject: Re: [parisc-linux] Second Draft of the help for the kernel options
Date: Wed, 03 Oct 2001 10:57:08 +0200	[thread overview]
Message-ID: <3BBAD2E4.3E802263@esiee.fr> (raw)
In-Reply-To: 200110021732.LAA07808@puffin.external.hp.com

Hi all,

	The Bjorn's idea is quite practical but the problem is we need to do a
complete list of command. With this list, users will know what commands
to do to get the cpu type...

	For the B132L, I need to do in cr. And for 712, "in" do not give you
the model of the cpu :(

Perhaps, we could a more general text saying:   1- You have to enter the
information menu by "in" (it seems to be general to all boxes)
						2- Here you need to find the command to get the revisions of your
chip/device. This must look like PAXXX0. For example this command is cr
for B132 and io for newer machines.

btw, we could add the complete list of the commands in the HOWTO.

This is a proposition. Tell me what you think of it. Thomas.
ESIEE Team

> >   Main Menu: Enter command or menu > in fru
> 
> For newer machines, "in io" at "Main Menu" prompt will list all IO devices.

  reply	other threads:[~2001-10-03  9:02 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-01 23:16 [parisc-linux] Second Draft of the help for the kernel options Thomas Marteau
2001-10-02 15:23 ` Bjorn Helgaas
2001-10-02 17:32   ` Grant Grundler
2001-10-03  8:57     ` Thomas Marteau [this message]
2001-10-07 23:31 ` Matthew Wilcox
2001-10-08  3:48   ` Grant Grundler
2001-10-08 14:44     ` Thomas Marteau
2001-10-08 14:58       ` Matthew Wilcox
  -- strict thread matches above, loose matches on Subject: below --
2001-10-02  6:12 Jurriaan Kalkman
2001-10-02  8:44 Jurij Smakov
2001-10-02  9:38 ` Richard Allen

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=3BBAD2E4.3E802263@esiee.fr \
    --to=marteaut@esiee.fr \
    --cc=bjorn_helgaas@hp.com \
    --cc=grundler@puffin.external.hp.com \
    --cc=parisc-linux@parisc-linux.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.