Re: [kbuild-devel] Configure.help entries wanted

Re: [kbuild-devel] Configure.help entries wanted

[Jaswinder Singh]

>
>   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

AFAIK WindowsCE machines are also broad term.

BTW, how many WindowsCE machines are fully (means all the features as
provided by Windows CE) supported by LinuxSH and how many machines are
partially(only few features) supported by LinuxSH ?

Thank you,

Best Regards,

Jaswinder.
--
These are my opinions not 3Di.

Re: [kbuild-devel] Configure.help entries wanted

[Greg Banks]

Jaswinder Singh wrote:
> 
> What is the companion chip in DMIDA ?

  HD64465.

> IrDA and USB are working properly in linux ?

  No.  IrDA seems easy, just haven't got around to it.
USB is a major pain on the HD64465 because of the way it
deals with "host" memory.  I had a driver which initialised
the root hub at one point but haven't had time to push
it any further.

Greg.
-- 
If it's a choice between being a paranoid, hyper-suspicious global
village idiot, or a gullible, mega-trusting sheep, I don't look
good in mint sauce.                      - jd, slashdot, 11Feb2000.

Re: [kbuild-devel] Configure.help entries wanted

[Jaswinder Singh]

"Greg Banks" <gnb@alphalink.com.au> wrote:

> 
>   Manufacturer = DataMyte, a division of Rockwell.
>   Machine = DataMyte Industrial Digital Assistant 4000
>             (aka DMIDA, www.dmida.com)
> 

What is the companion chip in DMIDA ?

IrDA and USB are working properly in linux ?

Thank you,

Best Regards,

Jaswinder.
--
These are my opinions not 3Di.

Re: [kbuild-devel] Configure.help entries wanted

[Greg Banks]

Alan Cox wrote:
> 
> >   Their co-operation came not from a spirit of enlightment but
> > because this was a commercial venture to port Linux to the box
> > to replace WinCE.  You can buy these with Linux now.
> 
> Including open source drivers for their touchscreen ?

  I believe so, but I only write the stuff.  We'll know for
sure when somebody actually buys one ;-)

Greg.
-- 
If it's a choice between being a paranoid, hyper-suspicious global
village idiot, or a gullible, mega-trusting sheep, I don't look
good in mint sauce.                      - jd, slashdot, 11Feb2000.

Re: [kbuild-devel] Configure.help entries wanted

[Jaswinder Singh]

"Greg Banks" <gnb@alphalink.com.au> wrote :


> Alan Cox wrote:
> > 
> > Including open source drivers for their touchscreen ?
> 
>   I believe so, but I only write the stuff.  We'll know for
> sure when somebody actually buys one ;-)
> 

Please send a copy to all of us ;)

Jaswinder.
--
These are my opinions not 3Di.

Re: [kbuild-devel] Configure.help entries wanted

[Alan Cox]

>   Their co-operation came not from a spirit of enlightment but
> because this was a commercial venture to port Linux to the box
> to replace WinCE.  You can buy these with Linux now.

Including open source drivers for their touchscreen ?

Re: [kbuild-devel] Configure.help entries wanted

[Greg Banks]

Pavel Machek wrote:
> 
> >   From the manufacturer.  We had the fullest possible co-operation [...]
> 
> Nice, *very* nice. What manufacturer / machine is that?

  Manufacturer = DataMyte, a division of Rockwell.
  Machine = DataMyte Industrial Digital Assistant 4000
            (aka DMIDA, www.dmida.com)

  Their co-operation came not from a spirit of enlightment but
because this was a commercial venture to port Linux to the box
to replace WinCE.  You can buy these with Linux now.

Greg.
-- 
If it's a choice between being a paranoid, hyper-suspicious global
village idiot, or a gullible, mega-trusting sheep, I don't look
good in mint sauce.                      - jd, slashdot, 11Feb2000.

Re: [kbuild-devel] Configure.help entries wanted

[Pavel Machek]

Hi!

> > >   I have some code which could become the basis for such a thing.
> > > It's a touch panel driver for the DMIDA but it also has a device-
> > > independent layer which does supersampling, scaling, provides
> > > raw and cooked Linux Input interfaces, and a /proc interface to
> > > allow the calibration app to control the scaling.
> > >
> > >   Unfortunately I can't release it yet for (ahem) legal reasons.
> > >
> > 
> > nice job , from where you get the related specs ?
> 
>   From the manufacturer.  We had the fullest possible co-operation
> including all technical specs, several sample machines, source to
> the WinCE drivers for the hardware, and engineers (including the lead
> hardware designer, a *very* cluey gentleman) on standby to answer
> questions.

Nice, *very* nice. What manufacturer / machine is that?
								Pavel
PS: If someone wants to develop, pr31700-based machines are pretty
well documented, because 99% of functionality comes from two core
chips, and they are documented.

-- 
I'm pavel@ucw.cz. "In my country we have almost anarchy and I don't care."
Panos Katsaloulis describing me w.r.t. patents at discuss@linmodems.org

Re: [kbuild-devel] Configure.help entries wanted

[Greg Banks]

Jaswinder Singh wrote:
> 
> 
> i even face problem in xscribble too , i think it donot likes my handwriting
> ;)

  Or anyone else's.

> Are you having sources of Calligrapher ?

  No.

> If no , i know that you can write better version then Calligrapher in Linux
> :)

  This would seem a perfect opportunity for sarcasm.

Greg.
-- 
If it's a choice between being a paranoid, hyper-suspicious global
village idiot, or a gullible, mega-trusting sheep, I don't look
good in mint sauce.                      - jd, slashdot, 11Feb2000.

Re: [kbuild-devel] Configure.help entries wanted

[Bill Pringlemeir]

 >>  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

>>>>> "JS" == Jaswinder Singh <jaswinder.singh@3disystems.com> writes:

 JS> AFAIK WindowsCE machines are also broad term.

Windows CE also implies that the device has an MMU.  As opposed to a
Revo (sp), Palm, etc. device.  I think that most Linux ports need the
MMU (ucLinux excluded)... Too technical a description in the help
wouldn't be much help at all, in my opinion.

regards,
Bill Pringlemeir.

Re: [kbuild-devel] Configure.help entries wanted

[Jaswinder Singh]

Dear Greg,

"Greg Banks" <gnb@alphalink.com.au> wrote :
>
>   Ok, I've found the description of this on handhelds.org, and
> it appears to be a derivative of xscribble, which I have tried.
> Unlike xscribble it does fullscreen mode, which is good, but
> it's still single-character and requires the user to learn
> how to write all over again.  In other words, like everything
> else available on Linux (and even MS's Jot) it's *crap* compared to
>

i even face problem in xscribble too , i think it donot likes my handwriting
;)

> http://www.paragraph.com/products/internetink/calligrapher/features.html
>
>   I would give my eye teeth for a Linux version of Calligrapher.
>

Are you having sources of Calligrapher ?

If no , i know that you can write better version then Calligrapher in Linux
:)

Happy Hacking !!

Jaswinder.
--
These are my opinions not 3Di.

Re: [kbuild-devel] Configure.help entries wanted

[Greg Banks]

Alan Cox wrote:
> 
> > Visual Studio, or the feature where you can have a decent handwriting
> > recognition system, or the feature where you can run Pocket {Internet
> > Explorer,Word} then the answer is none of them.
> 
> Handwriting recognition with fscrib works very well indeed.

  Ok, I've found the description of this on handhelds.org, and
it appears to be a derivative of xscribble, which I have tried.
Unlike xscribble it does fullscreen mode, which is good, but
it's still single-character and requires the user to learn
how to write all over again.  In other words, like everything
else available on Linux (and even MS's Jot) it's *crap* compared to

http://www.paragraph.com/products/internetink/calligrapher/features.html

  I would give my eye teeth for a Linux version of Calligrapher.

Greg.
-- 
If it's a choice between being a paranoid, hyper-suspicious global
village idiot, or a gullible, mega-trusting sheep, I don't look
good in mint sauce.                      - jd, slashdot, 11Feb2000.

Re: [kbuild-devel] Configure.help entries wanted

[Greg Banks]

Jaswinder Singh wrote:
> 
> "Greg Banks" <gnb@alphalink.com.au> wrote:
> >
> >   I have some code which could become the basis for such a thing.
> > It's a touch panel driver for the DMIDA but it also has a device-
> > independent layer which does supersampling, scaling, provides
> > raw and cooked Linux Input interfaces, and a /proc interface to
> > allow the calibration app to control the scaling.
> >
> >   Unfortunately I can't release it yet for (ahem) legal reasons.
> >
> 
> nice job , from where you get the related specs ?

  From the manufacturer.  We had the fullest possible co-operation
including all technical specs, several sample machines, source to
the WinCE drivers for the hardware, and engineers (including the lead
hardware designer, a *very* cluey gentleman) on standby to answer
questions.

  It makes an amazing difference to have all the nasty little
hardware quirks and known workarounds for them laid bare before you.

Greg.
-- 
If it's a choice between being a paranoid, hyper-suspicious global
village idiot, or a gullible, mega-trusting sheep, I don't look
good in mint sauce.                      - jd, slashdot, 11Feb2000.

Re: [kbuild-devel] Configure.help entries wanted

[Greg Banks]

esr@thyrsus.com wrote:
> 
> Greg Banks <gbanks@pocketpenguins.com>:
> >   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.
> 
> Since you asked...
> 
> # Choice: superhsys
> Generic
> CONFIG_SH_GENERIC
>   Select Generic if configuring for a generic SuperH system.

  The "generic" option compiles in *all* the possible hardware
support and relies on the sh_mv= kernel commandline option to choose
at runtime which routines to use.  "MV" stands for "machine vector";
each of the machines below is described by a machine vector and
the "generic" option chooses to compile them all in.

>   Select SolutionEngine if configuring for a Hitachi SH7709
>   or SH7750 evalutation board.
> 
>   Select Overdrive if configuring for a ST407750 Overdrive board.
>   More information at
>   <http://linuxsh.sourceforge.net/docs/7750overdrive.php3>
> 
>   Select HP620 if configuring for a HP Jornada HP620.
>   More information at
>   <http://www.hp.com/jornada>.
> 
>   Select HP680 if configuring for a HP Jornada HP680.
>   More information at
>   <http://www.hp.com/jornada/products/680>.
> 
>   Select HP690 if configuring for a HP Jornada HP690.
>   More information at <http://www.hp.com/jornada/products/680>.

  You won't get any information about Linux on Jornadas at HP.

> 
>   Select CqREEK if configuring for a CqREEK SH7708 or SH7750.
>   More information at
>   <http://sources.redhat.com/ecos/hardware.html#SuperH>.
> 
>   Select DMIDA if configuring for a DataMyte 4000 Industrial
>   Digital Assistant. More information at <http://www.dmida.com>.
> 
>   Select EC3104 if configuring for a system with an Eclipse
>   International EC3104 chip, e.g. the Harris AD2000.
> 
>   Select Dreamcast if configuring for a SEGA Dreamcast.
>   More information at
>   <http://www.m17n.org/linux-sh/dreamcast>.

  The Dreamcast project is at <http://linuxdc.sourceforge.net/>
They usually have slightly newer DC support than
linuxsh.sourceforge.net,
to which they sync regularly.

> 
>   Select BareCPU if you know what this means, and it applies
>   to your system.
> 
> Can you be any more explicit about the BareCPU option?

  "Bare CPU" aka "unknown" means an SH-based system which is not
one of the specific ones mentioned above, which means you need to
enter all sorts of stuff like CONFIG_MEMORY_START because the config
system doesn't already know what it is.  You get a machine vector
without any platform-specific code in it, so things like the RTC may
not work.

  This option is for the early stages of porting to a new machine.

  Basically the machine choices are laid out like this:

  generic = all of the known machines
  machine foo
  machine bar
  unknown = none of the known machines

> Physical memory start address
> CONFIG_MEMORY_START
>   The physical memory start address will be automatically
>   set to 08000000, unless you selected one of the following
>   processor types: SolutionEngine, Overdrive, HP620, HP680, HP690,
>   in which case the start address will be set to 0c000000.
> 
>   Do not change this address unless you know what you are doing.
> 
> Why might someone want to change this address?

  Only when porting to a new machine which is not already
known by the config system.  Changing it from the known correct
value on any of the known systems will only lead to disaster.

> Early printk support
> CONFIG_SH_EARLY_PRINTK
>   Say Y here to redirect kernel printks from the boot console to an
>   SCI serial console as soon as one is available.
> 
> This was my guess.  Is it correct?

  Nearly.

-  the serial console can be either SCI or SCIF (the latter has a FIFO)

-  the redirect happens *before* the serial console is available, and
   stops when the serial console is initialised

-  printks go to a BIOS conforming to the LinuxSH standard (i.e.
   the SH-IPL bootloader)

  Try:

Say Y here to redirect kernel messages to the serial port
used by the SH-IPL bootloader, starting very early in the boot
process and ending when the kernel's serial console is initialised.
This option is only useful porting the kernel to a new machine,
when the kernel may crash or hang before the serial console is
initialised.

> SuperH SCI (serial) support
> CONFIG_SH_SCI
>   Selecting this option will allow the Linux kernel to transfer
>   data over SCI (Serial Communication Interface) and/or SCIF
>   which are built into the Hitachi SuperH processor.
> 
>   If in doubt, press "y".
> 
> What data?  Is this just an on-board RS232C controller?

  Sorry, the description is unclear.  It's an on-CPU RS232 controller,
usually used as the console.  The option provides 1 to 3 (depending
on the CPU model) standard Linux tty devices, /dev/ttySC[012].

> 
> 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 (including calls to read and
>   write characters to a system console, get a MAC address from an
>   on-board Ethernet interface, and shut down the hardware).  Note this
>   does not work with machines with an existing operating system in
>   mask ROM and no flash (WindowsCE machines fall in this category).
>   If unsure, say N.
> 
> Note that I mixed in some information I gathered from reasding the source.
> Please check for correctness.

  That's fine.

Greg.
-- 
If it's a choice between being a paranoid, hyper-suspicious global
village idiot, or a gullible, mega-trusting sheep, I don't look
good in mint sauce.                      - jd, slashdot, 11Feb2000.

Re: [kbuild-devel] Configure.help entries wanted

[Jaswinder Singh]

"Greg Banks" <gnb@alphalink.com.au> wrote:
> 
>   I have some code which could become the basis for such a thing.
> It's a touch panel driver for the DMIDA but it also has a device-
> independent layer which does supersampling, scaling, provides
> raw and cooked Linux Input interfaces, and a /proc interface to
> allow the calibration app to control the scaling.
> 
>   Unfortunately I can't release it yet for (ahem) legal reasons.
> 

nice job , from where you get the related specs ?

Best Regards,

Jaswinder.
-- 
These are my opinions not 3Di.

Re: [kbuild-devel] Configure.help entries wanted

[Greg Banks]

Jaswinder Singh wrote:
> 
> "Alan Cox" <alan@lxorguk.ukuu.org.uk> wrote :
> 
> >
> > Handwriting recognition with fscrib works very well indeed.
> >
> 
> But not in Linux SH , there is so Touch Panel Interface in Linux SH yet :(

  I have some code which could become the basis for such a thing.
It's a touch panel driver for the DMIDA but it also has a device-
independent layer which does supersampling, scaling, provides
raw and cooked Linux Input interfaces, and a /proc interface to
allow the calibration app to control the scaling.

  Unfortunately I can't release it yet for (ahem) legal reasons.

  Anyway the limitation with handwriting recognition is not getting
the data out of the hardware but recognising the sample stream as
characters.  This is *difficult*.

Greg.
-- 
If it's a choice between being a paranoid, hyper-suspicious global
village idiot, or a gullible, mega-trusting sheep, I don't look
good in mint sauce.                      - jd, slashdot, 11Feb2000.

Re: [kbuild-devel] Configure.help entries wanted

[Jaswinder Singh]

"Greg Banks" <gnb@alphalink.com.au> wrote:
> > 
> > Can we use "HP Jornada 600 series" inspite of "WindowsCE machine" ?
> 
>   Sorry, I'm not sure what you mean here.
>

forget about it ;)
 
> 
>   But Compaq is playing nice in a way HP (or at least the division
> that makes Jornadas) isn't.  Furthermore the ARM port is older.
> 

Thats why Compaq's iPAQ are in much demand :)

Best Regards,

Jaswinder.
-- 
These are my opinions not 3Di.

Re: [kbuild-devel] Configure.help entries wanted

[Greg Banks]

Jaswinder Singh wrote:
> 
> Can we use "HP Jornada 600 series" inspite of "WindowsCE machine" ?

  Sorry, I'm not sure what you mean here.

> BTW, in Jornada 600 series only Keyboard and LCD is working and some CPU
> related stuff  which we can found in Hitachi Manuals , thats it .
>
> But linux-arm is supporting full iPAQ hardware .

  But Compaq is playing nice in a way HP (or at least the division
that makes Jornadas) isn't.  Furthermore the ARM port is older.

Greg.
-- 
If it's a choice between being a paranoid, hyper-suspicious global
village idiot, or a gullible, mega-trusting sheep, I don't look
good in mint sauce.                      - jd, slashdot, 11Feb2000.

Re: [kbuild-devel] Configure.help entries wanted

[Greg Banks]

Alan Cox wrote:
> 
> > [...] or the feature where you can have a decent handwriting
> > recognition system,[...]
> 
> Handwriting recognition with fscrib works very well indeed.

  I haven't tried that one.  Does it do cursive writing,
with dictionary assistance, on the X root window?

Greg.
-- 
If it's a choice between being a paranoid, hyper-suspicious global
village idiot, or a gullible, mega-trusting sheep, I don't look
good in mint sauce.                      - jd, slashdot, 11Feb2000.

Re: [kbuild-devel] Configure.help entries wanted

[Jaswinder Singh]

esr@thyrsus.com wrote :

>   Select HP620 if configuring for a HP Jornada HP620.
>   More information at
>   <http://www.hp.com/jornada>.
> 
>   Select HP680 if configuring for a HP Jornada HP680.
>   More information at
>   <http://www.hp.com/jornada/products/680>.
> 
>   Select HP690 if configuring for a HP Jornada HP690.
>   More information at <http://www.hp.com/jornada/products/680>.
> 

Have you asked from HP , are they ready to support Linux ?

Thank you ,

Best Regards,

Jaswinder.
-- 
These are my opinions not 3Di.

Re: [kbuild-devel] Configure.help entries wanted

[Jaswinder Singh]

"Alan Cox" <alan@lxorguk.ukuu.org.uk> wrote :


> 
> Handwriting recognition with fscrib works very well indeed.
> 

But not in Linux SH , there is so Touch Panel Interface in Linux SH yet :(

Thank you,

Best Regards,

Jaswinder.
-- 
These are my opinions not 3Di.

Re: [kbuild-devel] Configure.help entries wanted

[Greg Banks]

Jaswinder Singh wrote:
> 
> "Greg Banks" <gbanks@pocketpenguins.com> wrote:

  (I'm posting from a different address because kernel.org had
some difficulties with pocketpenguins.com)

> > Jaswinder Singh wrote:
> > >
> > > >
> > > BTW, how many WindowsCE machines are fully (means all the features as
> > > provided by Windows CE) supported by LinuxSH and how many machines are
> > > partially(only few features) supported by LinuxSH ?
> >
> >   I don't understand, what features do you mean?
> >
> 
> By features , i mean , that we can use all the hardware of WindowsCE machine
> , like Touch panel , modem , IrDA, Sound , etc , etc .

  Modems are tricky, because they're frequently WinModems which
have a whole lot of well-known issues.  Other features depend on
the speed at which they can be reverse engineered, as most
WinCE manufacturers don't co-operate.  I'd be surprised if any
WindowsCE machine's hardware was fully supported by LinuxSH yet,
but I don't have a full list anywhere (sorry).  I'd guess the HP
Jornada 600 series are probably best supported.

Greg.
-- 
If it's a choice between being a paranoid, hyper-suspicious global
village idiot, or a gullible, mega-trusting sheep, I don't look
good in mint sauce.                      - jd, slashdot, 11Feb2000.

Re: [kbuild-devel] Configure.help entries wanted

[Jaswinder Singh]

Dear Greg,

>
>   Modems are tricky, because they're frequently WinModems which
> have a whole lot of well-known issues.  Other features depend on
> the speed at which they can be reverse engineered, as most
> WinCE manufacturers don't co-operate.  I'd be surprised if any
> WindowsCE machine's hardware was fully supported by LinuxSH yet,
> but I don't have a full list anywhere (sorry).  I'd guess the HP
> Jornada 600 series are probably best supported.
>

yes , this is what i am looking for :)

Can we use "HP Jornada 600 series" inspite of "WindowsCE machine" ?

BTW, in Jornada 600 series only Keyboard and LCD is working and some CPU
related stuff  which we can found in Hitachi Manuals , thats it .

But linux-arm is supporting full iPAQ hardware .

Thank you,

Best Regards,

Jaswinder.
--
These are my opinions not 3Di.

Re: [kbuild-devel] Configure.help entries wanted

[Alan Cox]

> Visual Studio, or the feature where you can have a decent handwriting
> recognition system, or the feature where you can run Pocket {Internet
> Explorer,Word} then the answer is none of them.

Handwriting recognition with fscrib works very well indeed.

Re: [kbuild-devel] Configure.help entries wanted

[Greg Banks]

Jaswinder Singh wrote:
> 
> >
> BTW, how many WindowsCE machines are fully (means all the features as
> provided by Windows CE) supported by LinuxSH and how many machines are
> partially(only few features) supported by LinuxSH ?

  I don't understand, what features do you mean?

  If you include the feature where you can write your code in MS
Visual Studio, or the feature where you can have a decent handwriting
recognition system, or the feature where you can run Pocket {Internet
Explorer,Word} then the answer is none of them.

Greg.
-- 
These are my opinions not PPIs.

Re: [kbuild-devel] Configure.help entries wanted

[Jaswinder Singh]

"Greg Banks" <gbanks@pocketpenguins.com> wrote:

> Jaswinder Singh wrote:
> >
> > >
> > BTW, how many WindowsCE machines are fully (means all the features as
> > provided by Windows CE) supported by LinuxSH and how many machines are
> > partially(only few features) supported by LinuxSH ?
>
>   I don't understand, what features do you mean?
>

By features , i mean , that we can use all the hardware of WindowsCE machine
, like Touch panel , modem , IrDA, Sound , etc , etc .

Thank you,

Best Regards,

Jaswinder.
--
These are my opinions not 3Di.

Re: [kbuild-devel] Configure.help entries wanted

[esr]

Greg Banks <gbanks@pocketpenguins.com>:
>   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.

Since you asked...

# Choice: superhsys
Generic
CONFIG_SH_GENERIC
  Select Generic if configuring for a generic SuperH system.

  Select SolutionEngine if configuring for a Hitachi SH7709
  or SH7750 evalutation board.

  Select Overdrive if configuring for a ST407750 Overdrive board.
  More information at
  <http://linuxsh.sourceforge.net/docs/7750overdrive.php3>

  Select HP620 if configuring for a HP Jornada HP620.
  More information at
  <http://www.hp.com/jornada>.

  Select HP680 if configuring for a HP Jornada HP680.
  More information at
  <http://www.hp.com/jornada/products/680>.

  Select HP690 if configuring for a HP Jornada HP690.
  More information at <http://www.hp.com/jornada/products/680>.

  Select CqREEK if configuring for a CqREEK SH7708 or SH7750.
  More information at
  <http://sources.redhat.com/ecos/hardware.html#SuperH>.

  Select DMIDA if configuring for a DataMyte 4000 Industrial
  Digital Assistant. More information at <http://www.dmida.com>.

  Select EC3104 if configuring for a system with an Eclipse
  International EC3104 chip, e.g. the Harris AD2000.

  Select Dreamcast if configuring for a SEGA Dreamcast.
  More information at
  <http://www.m17n.org/linux-sh/dreamcast>.

  Select BareCPU if you know what this means, and it applies
  to your system.

Can you be any more explicit about the BareCPU option?

Physical memory start address
CONFIG_MEMORY_START
  The physical memory start address will be automatically
  set to 08000000, unless you selected one of the following
  processor types: SolutionEngine, Overdrive, HP620, HP680, HP690,
  in which case the start address will be set to 0c000000.

  Do not change this address unless you know what you are doing.

Why might someone want to change this address?

Early printk support
CONFIG_SH_EARLY_PRINTK
  Say Y here to redirect kernel printks from the boot console to an
  SCI serial console as soon as one is available.

This was my guess.  Is it correct?

SuperH SCI (serial) support
CONFIG_SH_SCI
  Selecting this option will allow the Linux kernel to transfer
  data over SCI (Serial Communication Interface) and/or SCIF
  which are built into the Hitachi SuperH processor.
  
  If in doubt, press "y".

What data?  Is this just an on-board RS232C controller?

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 (including calls to read and
  write characters to a system console, get a MAC address from an
  on-board Ethernet interface, and shut down the hardware).  Note this
  does not work with machines with an existing operating system in
  mask ROM and no flash (WindowsCE machines fall in this category).
  If unsure, say N.

Note that I mixed in some information I gathered from reasding the source.
Please check for correctness.
-- 
		<a href="http://www.tuxedo.org/~esr/">Eric S. Raymond</a>

The whole of the Bill [of Rights] is a declaration of the right of the
people at large or considered as individuals...  It establishes some
rights of the individual as unalienable and which consequently, no
majority has a right to deprive them of.
         -- Albert Gallatin, Oct 7 1789

Re: [kbuild-devel] Configure.help entries wanted

[Jaswinder Singh]

>
>   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

AFAIK WindowsCE machines are also broad term.

BTW, how many WindowsCE machines are fully (means all the features as
provided by Windows CE) supported by LinuxSH and how many machines are
partially(only few features) supported by LinuxSH ?

Thank you,

Best Regards,

Jaswinder.
--
These are my opinions not 3Di.

Re: [kbuild-devel] Configure.help entries wanted

[Greg Banks]

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.

Re: [kbuild-devel] Configure.help entries wanted

[Jaswinder Singh]

Dear Greg,

>
> 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.

Thanks ,

Best Regards,

Jaswinder.
--
These are my opinions not 3Di.

Re: [kbuild-devel] Configure.help entries wanted

[Greg Banks]

Eric S. Raymond wrote:
> 
> CONFIG_SH_SCI
> CONFIG_SH_STANDARD_BIOS
> CONFIG_DEBUG_KERNEL_WITH_GDB_STUB

  From the LinuxSH CVS (I can write new ones if these are inadequate):

SuperH SCI (serial) support
CONFIG_SH_SCI
  Selecting this option will allow the Linux kernel to transfer
  data over SCI (Serial Communication Interface) and/or SCIF
  which are built into the Hitachi SuperH processor.

  If in doubt, press "y".

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.

GDB Stub kernel debug
CONFIG_DEBUG_KERNEL_WITH_GDB_STUB
  If you say Y here, it will be possible to remotely debug the SuperH
  kernel using gdb, if you have the gdb-sh-stub package from
  www.m17n.org (or any conforming standard LinuxSH BIOS) in FLASH or
  EPROM.  This enlarges your kernel image disk size by several megabytes
  but allows you to load, run and debug the kernel image remotely using
  gdb.  This is only useful for kernel hackers.  If unsure, say N.


Greg.
-- 
These are my opinions not PPIs.