Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Pete Popov <ppopov@pacbell.net>
To: sjhill@cotw.com
Cc: linux-mips@oss.sgi.com
Subject: Re: Documentation on MIPS kernel options...
Date: Sat, 07 Jul 2001 12:23:26 -0700	[thread overview]
Message-ID: <3B4761AE.3040601@pacbell.net> (raw)
In-Reply-To: 3B473ABF.F2444CEE@cotw.com

Steven J. Hill wrote:

> Greetings.
> 
> I have been having some correspondance with Eric Raymond (ESR)
> concerning MIPS configuration options. I have already sent him
> a fairly good sized list of descriptions for some MIPS options
> that will be utilized in the CML2 build system for the 2.5.x
> and 2.6.x series kernels. He sent me another list of items and
> I decided to ask those of you on the list to provide the
> descriptions. Please send me the descriptions and at the end of
> next week I will compile the results and send them off to 
> Eric. Thanks.
> 
> -Steve
 
> CONFIG_ARC_CONSOLE
> CONFIG_AU1000_UART

The uart on the Alchemy Au1000 is almost a 16550 but not quite.  I've 
added support for that uart in the non-standard uart section in 
drivers/char/Config.in.  This option is needed if you want uart support 
for debug and/or serial console.


> CONFIG_EVB_PCI1
> CONFIG_FORWARD_KEYBOARD
> CONFIG_GDB_CONSOLE



> CONFIG_IT8172_REVC

An older version of the IT8172 system controller what has slightly 
different pci mem windows. However, I don't think we need to support 
this anymore so I plan on dumping this asap.


> CONFIG_IT8172_SCR0
> CONFIG_IT8172_SCR1

On the IT8172 system controller, Smart Card Reader 0 and 1.


> CONFIG_SYSCLK_100
> CONFIG_SYSCLK_75
> CONFIG_SYSCLK_83


Let me know if you need additional information.

Thanks,

Pete


 
 

      parent reply	other threads:[~2001-07-07 19:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-07 16:37 Documentation on MIPS kernel options Steven J. Hill
2001-07-07 18:51 ` Keith M Wesolowski
2001-07-07 19:23 ` Pete Popov [this message]

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=3B4761AE.3040601@pacbell.net \
    --to=ppopov@pacbell.net \
    --cc=linux-mips@oss.sgi.com \
    --cc=sjhill@cotw.com \
    /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