Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Sergei Shtylylov <sshtylyov@ru.mvista.com>
To: Linux MIPS Development <linux-mips@linux-mips.org>
Cc: Ralf Baechle <ralf@linux-mips.org>
Subject: Re: JMR3927
Date: Tue, 15 Nov 2005 18:52:27 +0300	[thread overview]
Message-ID: <437A043B.6040604@ru.mvista.com> (raw)
In-Reply-To: <20051114114615.GA6186@linux-mips.org>

Hello.

Ralf Baechle wrote:

> Does anybody still care about the JMR3927 board?

    At least there's no 2.6 release planned for this board by Montavista.

>  The board code is pretty
> badly broken.   It's also currently the only user of the TX3927 in the tree.

   I saw you were busy with TX3927 maintenance recently... Looks like this is 
another chance to remind you of my old patch:

http://www.linux-mips.org/archives/linux-mips/2004-10/msg00300.html

>   Ralf

WBR, Sergei

  reply	other threads:[~2005-11-15 15:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-14 11:46 JMR3927 Ralf Baechle
2005-11-15 15:52 ` Sergei Shtylylov [this message]
2005-11-15 16:10   ` JMR3927 Ralf Baechle

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=437A043B.6040604@ru.mvista.com \
    --to=sshtylyov@ru.mvista.com \
    --cc=linux-mips@linux-mips.org \
    --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