linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Murray Jensen <Murray.Jensen@cmst.csiro.au>
To: msokolov@ivan.Harhan.ORG (Michael Sokolov)
Cc: linux-galileo@source.mvista.com, linuxppc-dev@lists.linuxppc.org
Subject: Re: [Linux-galileo] Re: EV-64260-BP & GT64260 bi_recs
Date: Mon, 25 Mar 2002 18:44:31 +1100	[thread overview]
Message-ID: <17636.1017042271@msa.cmst.csiro.au> (raw)
In-Reply-To: Message from msokolov@ivan.Harhan.ORG (Michael Sokolov) of "Sun, 24 Mar 2002 22:47:19 PST." <0203250647.AA26997@ivan.Harhan.ORG>


On Sun, 24 Mar 02 22:47:19 PST, msokolov@ivan.Harhan.ORG (Michael Sokolov) writes:
>It is wrong. Every platform in 2_4_devel my hacky hands have touched uses
>bi_recs exclusively. bi_recs work very well for me as they are right now.

Which part of "very limited and only used by certain platforms" is wrong? OK,
maybe its half-and-half then (half the platforms use them, half don't) - that's
a long way from all platforms. The proposal is that 2.5 use bi_recs exclusively
for all platforms (something I agree with, by the way). The discussion is in the
detail of the implementation.

>For me it has been ironed out perfectly a long time ago, which is why I haven't
>participated much in that "discussion".

Well, you'd better get involved then - because the proposal is to change them
(or maybe "extend slightly in a backwards compatible way", would better describe
it) so if they're perfect for you now, you wouldn't want this :-) I think they
are too limited at the moment, but could be very useful if implemented properly.
benh's current proposal appears to give me all that I want (except for some
formal definition of "dimension"), so I support it. Cheers!
								Murray...
--
Murray Jensen, CSIRO Manufacturing Sci & Tech,         Phone: +61 3 9662 7763
Locked Bag No. 9, Preston, Vic, 3072, Australia.         Fax: +61 3 9662 7853
Internet: Murray.Jensen@csiro.au

Hymod project: http://www.msa.cmst.csiro.au/projects/Hymod/


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

  reply	other threads:[~2002-03-25  7:44 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-25  6:47 [Linux-galileo] Re: EV-64260-BP & GT64260 bi_recs Michael Sokolov
2002-03-25  7:44 ` Murray Jensen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-03-25  4:31 Michael Sokolov
2002-03-25  6:30 ` Murray Jensen
2002-03-25  4:19 Michael Sokolov
2002-03-25 11:10 ` Nye Liu
2002-03-20 17:04 Michael Sokolov
2002-03-21 20:36 ` Troy Benjegerdes
2002-03-21 19:17   ` Mark A. Greer
2002-03-21 21:36     ` Jim Potter
2002-03-21 22:15       ` [Linux-galileo] " Nye Liu
2002-03-21 20:19         ` Mark A. Greer
2002-03-20  1:02 Michael Sokolov
2002-03-21 20:15 ` [Linux-galileo] " Troy Benjegerdes
2002-03-21 19:10   ` Mark A. Greer
2002-03-21 22:10     ` Nye Liu

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=17636.1017042271@msa.cmst.csiro.au \
    --to=murray.jensen@cmst.csiro.au \
    --cc=linux-galileo@source.mvista.com \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=msokolov@ivan.Harhan.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;
as well as URLs for NNTP newsgroup(s).