Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
To: Linux-MIPS <linux-mips@linux-mips.org>
Cc: Ralf Baechle <ralf@linux-mips.org>,
	Manish Lachwani <mlachwani@mvista.com>,
	anemo@mba.ocn.ne.jp
Subject: Re: [PATCH] TX49 has write buffer
Date: Sat, 19 Aug 2006 20:36:13 +0400	[thread overview]
Message-ID: <44E73DFD.5030404@ru.mvista.com> (raw)
In-Reply-To: <44E64687.7000704@ru.mvista.com>

Hello.

Sergei Shtylyov wrote:

> TX49 CPUs have a write buffer, so we need to select CPU_HAS_WB -- 
> otherwise all Toshiba RBTX49xx kernels fail to build.

    The uptimate reason is I think that <asm/system.h> doesn't include 
<asm/wbflush.h> if CONFIG_CPU_HAS_WB is undefined -- although, <asm/wbflush.h> 
handles this situation itself. Well, <asm/system.h> doesn't need the wbflush() 
macro in that case, so it's in his own right to not include that header...

WBR, Sergei

  parent reply	other threads:[~2006-08-19 16:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-18 23:00 [PATCH] TX49 has write buffer Sergei Shtylyov
2006-08-19 14:11 ` Atsushi Nemoto
2006-08-19 16:04   ` Sergei Shtylyov
2006-08-19 16:36 ` Sergei Shtylyov [this message]
2006-08-20 13:55   ` Atsushi Nemoto

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=44E73DFD.5030404@ru.mvista.com \
    --to=sshtylyov@ru.mvista.com \
    --cc=anemo@mba.ocn.ne.jp \
    --cc=linux-mips@linux-mips.org \
    --cc=mlachwani@mvista.com \
    --cc=ralf@linux-mips.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