public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: george anzinger <george@mvista.com>
To: "David S. Miller" <davem@redhat.com>
Cc: sam@ravnborg.org, akpm@zip.com.au,
	kbuild-devel@lists.sourceforge.net, mec@shout.net,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] asm-generic magic
Date: Wed, 07 May 2003 08:33:27 -0700	[thread overview]
Message-ID: <3EB92747.2070204@mvista.com> (raw)
In-Reply-To: <20030507.070646.54208027.davem@redhat.com>

David S. Miller wrote:
>    From: george anzinger <george@mvista.com>
>    Date: Wed, 07 May 2003 08:08:38 -0700
>    
>    Also, if you are introducing a file with asm code, you either cause
>    all "other" archs to fail (till they catch up) or you must
>    introduce the simple one line file in each arch.
> 
> This is desirable behavior, then the arch maintainer sees the breakage
> and if the asm-generic solution is appropriate he makes that
> decision.
> 
> I don't think you want to play expert for port maintainers.
> 
> I sense that you want to be able to do "instant ports" to
> some architecture.  This isn't the way to do it.  Instead
> tar up a template set of asm-foo/ header files, and dump that
> into the directory for your new port.

For the record, I don't and have not done ports.

Rather I was interested in introducing a scaled math header.  It would 
contain routines to allow access to the 64 bit mpy and div 
instructions, which ,of course, can be done in C but, if you don't 
want the 64-bit lib, must be done with a rather large bit of code to 
do simple s32=s64/s32 and s32=s64%s32 calculations.  And, on 64-bit 
archs the whole problem goes away.
> 
> I see absolutely no value whatsoever to what you are proposing.
> In fact, I frankly think it sucks. :(

I understand what you think, but don't understand why you think that :(
> 
> 

-- 
George Anzinger   george@mvista.com
High-res-timers:  http://sourceforge.net/projects/high-res-timers/
Preemption patch: http://www.kernel.org/pub/linux/kernel/people/rml


  reply	other threads:[~2003-05-07 15:21 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-06  6:41 [PATCH] asm-generic magic george anzinger
2003-05-06  7:26 ` David S. Miller
2003-05-06 20:15   ` george anzinger
2003-05-07  2:55     ` David S. Miller
2003-05-07  9:35       ` george anzinger
2003-05-07 14:30         ` Sam Ravnborg
2003-05-07 15:08           ` george anzinger
2003-05-07 14:06             ` David S. Miller
2003-05-07 15:33               ` george anzinger [this message]
2003-05-07 14:31                 ` David S. Miller
2003-05-07 15:24           ` Kbuild newbie/promotional docs needed John van V.
2003-05-07 20:24             ` Sam Ravnborg

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=3EB92747.2070204@mvista.com \
    --to=george@mvista.com \
    --cc=akpm@zip.com.au \
    --cc=davem@redhat.com \
    --cc=kbuild-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mec@shout.net \
    --cc=sam@ravnborg.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