All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Linh Dang" <linhd@nortelnetworks.com>
To: <linuxppc-embedded@lists.linuxppc.org>
Subject: BAT mapping
Date: Tue, 29 Jun 2004 11:23:51 -0400	[thread overview]
Message-ID: <wn5isdatmk8.fsf@linhd-2.ca.nortel.com> (raw)
In-Reply-To: <1088518106.14216.1415.camel@hades.cambridge.redhat.com> (David Woodhouse's message of "Tue, 29 Jun 2004 10:08:27 -0400")


Hi,

I'm porting Linux to our proprietary boards. it's 7447-based with
gt64260 bridge. We used vanilla 2.6.7 from kernel.org. It worked out
well (2 person/grunt/slave-dats to get it linux booted and with
nfs/telnet/gdb...) thank you very much for your work.

In the porting process, we change the bat mapping to used all the 8
DBAT registers. our new algorithm is quite generic and will work for
cpu without hi_bats as well. My question is why it was NOT done this
way but hard-coded to bat2 and bat3. Am I missing some subtle things?

Thanx

--
Linh Dang


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2004-06-29 15:23 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-20 20:27 GT64260_eth (Ethernet) Driver Dieu Morales
2004-06-23 22:39 ` Mark A. Greer
2004-06-24  8:37   ` David Woodhouse
2004-06-24 11:23     ` Brian Waite
2004-06-24 18:46     ` Mark A. Greer
2004-06-24 19:02       ` Mark A. Greer
2004-06-25  7:10       ` David Woodhouse
2004-06-25 22:05         ` Mark A. Greer
2004-06-25 23:43           ` David Woodhouse
2004-06-26  0:07             ` Mark A. Greer
2004-06-26  0:41               ` Paul Mackerras
2004-06-26  1:47                 ` Mark A. Greer
2004-07-29  3:19                   ` Dieu Morales
2004-07-29 17:28                     ` Mark A. Greer
2004-06-29 14:08               ` David Woodhouse
2004-06-29 15:23                 ` Linh Dang [this message]
2004-06-29 17:59                   ` BAT mapping Linh Dang

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=wn5isdatmk8.fsf@linhd-2.ca.nortel.com \
    --to=linhd@nortelnetworks.com \
    --cc=linuxppc-embedded@lists.linuxppc.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.