public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: esr@thyrsus.com
Cc: Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: Configure.help missing entries list
Date: Tue, 20 Nov 2001 15:10:07 +0000	[thread overview]
Message-ID: <25065.1006269007@redhat.com> (raw)
In-Reply-To: <20011120095018.A25289@thyrsus.com>
In-Reply-To: <20011120095018.A25289@thyrsus.com>


esr@thyrsus.com said:
> It's down to 145 entries from 167 last week, thanks mostly to David
> Woodhouse documenting the new MTD symbols.  Please do what you can to
> empty this list by sending me help entries. 

You missed three that I sent you before. If you don't like my version of 
CONFIG_MEMORY_SET I'm sure you can come up with a new one - but the other 
two ought to be acceptable.


Physical memory size
CONFIG_MEMORY_SIZE
  This sets the default memory size assumed by your SH kernel. It can 
  be overridden as normal by the 'mem=' argument on the kernel command
  line. If unsure, consult your board specifications or just leave it
  as 0x00400000 which was the default value before this became
  configurable.

Darkness
CONFIG_MEMORY_SET
  This is an option about which you will never be asked a question. 
  Therefore, I conclude that you do not exist - go away.

  There is a grue here.

Cache and PCI noncoherent
CONFIG_SH_PCIDMA_NONCOHERENT
  Enable this option if your platform does not have a CPU cache which
  remains coherent with PCI DMA. It is safest to say 'Y', although you
  will see better performance if you can say 'N', because the PCI DMA 
  code will not have to flush the CPU's caches. If you have a PCI host
  bridge integrated with your SH CPU, refer carefully to the chip specs
  to see if you can say 'N' here. Otherwise, leave it as 'Y'.



--
dwmw2



  reply	other threads:[~2001-11-20 15:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-20 14:50 Configure.help missing entries list Eric S. Raymond
2001-11-20 15:10 ` David Woodhouse [this message]
2001-11-20 15:12   ` Eric S. Raymond
2001-11-20 15:44     ` Eric S. Raymond
2001-11-20 16:16 ` Tom Rini

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=25065.1006269007@redhat.com \
    --to=dwmw2@infradead.org \
    --cc=esr@thyrsus.com \
    --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