public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Banks <gbanks@pocketpenguins.com>
To: Jaswinder Singh <jaswinder.singh@3disystems.com>
Cc: esr@thyrsus.com, CML2 <linux-kernel@vger.kernel.org>,
	kbuild-devel@lists.sourceforge.net
Subject: Re: [kbuild-devel] Configure.help entries wanted
Date: Sat, 26 May 2001 20:06:58 +1000	[thread overview]
Message-ID: <3B0F8042.90DD5C5D@pocketpenguins.com> (raw)
In-Reply-To: <20010525012200.A5259@thyrsus.com> <3B0F3268.A671BC7A@pocketpenguins.com> <002401c0e5aa$0049a000$47a6b3d0@Toshiba>

Jaswinder Singh wrote:
> 
> > Use LinuxSH standard BIOS
> > CONFIG_SH_STANDARD_BIOS
> >   Say Y here if your target has the gdb-sh-stub package from
> >   www.m17n.org (or any conforming standard LinuxSH BIOS) in FLASH
> >   or EPROM.  The kernel will use standard BIOS calls during boot
> >   for various housekeeping tasks.  Note this does not work with
> >   WindowsCE machines.  If unsure, say N.
> >
> 
> "WindowsCE" word looks very abrupt in Linux's Configure.help, Please use
> some better word inspite of it like HandHeld Devices or PDAs.

  The class of machines for which this option does not apply is
"machines with an existing operating system in mask rom and no
flash", which AFAICT is equivalent to "WindowsCE machines
".  The
class "handheld devices" is too broad as it includes machines
like the Rockwell DMIDA which is handheld but has flash.  So
this seems to me to be a reasonably good choice of words.

  Having said that, I agree that the help text entries for the SH
port are in general of less than stellar quality, for various 
(mostly good) reasons.  I'm hoping ESR will give us some editorial
feedback which will provide a good excuse to fix them.

Greg.
-- 
These are my opinions not PPIs.

  reply	other threads:[~2001-05-26 23:03 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-25  5:22 Configure.help entries wanted Eric S. Raymond
2001-05-25  6:03 ` Keith Owens
2001-05-25  6:35   ` Eric S. Raymond
2001-05-25  6:59     ` Keith Owens
2001-05-25  7:10       ` Eric S. Raymond
2001-05-25  7:36 ` Philip Blundell
2001-05-25  8:04   ` [kbuild-devel] " Eric S. Raymond
2001-05-25 10:30     ` Russell King
2001-05-26  4:34 ` [kbuild-devel] " Greg Banks
2001-05-26  6:06   ` Jaswinder Singh
2001-05-26 10:06     ` Greg Banks [this message]
2001-05-26 18:50       ` Jaswinder Singh
2001-05-27  1:12         ` Greg Banks
2001-05-27  1:08           ` Jaswinder Singh
2001-05-27  1:29             ` Greg Banks
2001-05-27  1:28               ` Jaswinder Singh
2001-05-27  2:03                 ` Greg Banks
2001-05-27  2:08                   ` Jaswinder Singh
2001-05-27  1:20           ` Alan Cox
2001-05-27  1:31             ` Jaswinder Singh
2001-05-27  2:10               ` Greg Banks
2001-05-27  2:13                 ` Jaswinder Singh
2001-05-27  2:52                   ` Greg Banks
2001-05-27 16:27                     ` Pavel Machek
2001-05-28  0:56                       ` Greg Banks
2001-05-28  1:05                         ` Alan Cox
2001-05-28  2:36                           ` Greg Banks
2001-05-28  2:34                             ` Jaswinder Singh
2001-05-28  2:58                         ` Jaswinder Singh
2001-05-28  3:17                           ` Greg Banks
2001-05-27  2:00             ` Greg Banks
2001-05-27  3:06             ` Greg Banks
2001-05-27  3:10               ` Jaswinder Singh
2001-05-27 15:24                 ` Greg Banks
2001-05-27  5:03         ` Bill Pringlemeir
2001-05-26 21:48       ` esr
2001-05-27  1:54         ` Jaswinder Singh
2001-05-27  2:43         ` Greg Banks
  -- strict thread matches above, loose matches on Subject: below --
2001-05-26 20:13 Jaswinder Singh

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=3B0F8042.90DD5C5D@pocketpenguins.com \
    --to=gbanks@pocketpenguins.com \
    --cc=esr@thyrsus.com \
    --cc=jaswinder.singh@3disystems.com \
    --cc=kbuild-devel@lists.sourceforge.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox