Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
To: Yoichi Yuasa <yoichi_yuasa@tripeaks.co.jp>
Cc: Ralf Baechle <ralf@linux-mips.org>,
	linux-mips <linux-mips@linux-mips.org>
Subject: Re: [PATCH] add "depends on BROKEN" to broken boards support
Date: Fri, 06 Oct 2006 22:31:15 +0400	[thread overview]
Message-ID: <4526A0F3.5090202@ru.mvista.com> (raw)
In-Reply-To: <20061007005452.45b50d8c.yoichi_yuasa@tripeaks.co.jp>

Hello.

Yoichi Yuasa wrote:

> This patch has added "depends on BROKEN" to broken boards support.
> These boards cannot build now.

> Yoichi

> Signed-off-by: Yoichi Yuasa <yoichi_yuasa@tripeaks.co.jp>

> @@ -511,6 +517,7 @@ config QEMU
>  
>  config MARKEINS
>  	bool "Support for NEC EMMA2RH Mark-eins"
> +	depends on BROKEN
>  	select DMA_NONCOHERENT
>  	select HW_HAS_PCI
>  	select IRQ_CPU

    What's broken about this board?

> @@ -717,6 +724,7 @@ config SNI_RM200_PCI
>  
>  config TOSHIBA_JMR3927
>  	bool "Toshiba JMR-TX3927 board"
> +	depends on BROKEN
>  	select DMA_NONCOHERENT
>  	select HW_HAS_PCI
>  	select MIPS_TX3927
> @@ -728,6 +736,7 @@ config TOSHIBA_JMR3927
>  
>  config TOSHIBA_RBTX4927
>  	bool "Toshiba TBTX49[23]7 board"
> +	depends on BROKEN
>  	select DMA_NONCOHERENT
>  	select HAS_TXX9_SERIAL
>  	select HW_HAS_PCI

    ... and this one?

> @@ -745,6 +754,7 @@ config TOSHIBA_RBTX4927
>  
>  config TOSHIBA_RBTX4938
>  	bool "Toshiba RBTX4938 board"
> +	depends on BROKEN
>  	select HAVE_STD_PC_SERIAL_PORT
>  	select DMA_NONCOHERENT
>  	select GENERIC_ISA_DMA

    There's a patch from Atsushi Nemoto still pending commit, IIRC...

WBR, Sergei

  reply	other threads:[~2006-10-06 18:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-06 15:54 [PATCH] add "depends on BROKEN" to broken boards support Yoichi Yuasa
2006-10-06 18:31 ` Sergei Shtylyov [this message]
2006-10-06 21:48   ` Yoichi Yuasa
2006-10-07 13:55     ` Atsushi Nemoto
2006-10-07  4:02       ` Yoichi Yuasa

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=4526A0F3.5090202@ru.mvista.com \
    --to=sshtylyov@ru.mvista.com \
    --cc=linux-mips@linux-mips.org \
    --cc=ralf@linux-mips.org \
    --cc=yoichi_yuasa@tripeaks.co.jp \
    /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