All of lore.kernel.org
 help / color / mirror / Atom feed
From: "J . A . Magallon" <jamagallon@able.es>
To: Sergey Kubushin <ksi@cyberbills.com>
Cc: "J . A . Magallon" <jamagallon@able.es>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>,
	linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.2ac12
Date: Tue, 6 Mar 2001 00:30:56 +0100	[thread overview]
Message-ID: <20010306003056.C1136@werewolf.able.es> (raw)
In-Reply-To: <20010305235629.A1136@werewolf.able.es> <Pine.LNX.4.31ksi3.0103051507140.12620-100000@nomad.cyberbills.com>
In-Reply-To: <Pine.LNX.4.31ksi3.0103051507140.12620-100000@nomad.cyberbills.com>; from ksi@cyberbills.com on Tue, Mar 06, 2001 at 00:13:24 +0100


On 03.06 Sergey Kubushin wrote:
> On Mon, 5 Mar 2001, J . A . Magallon wrote:
> 
> > What that line does is to build a tool (aicasm) to generate the ucode
> > that
> > is built into the kernel (afaik, it is a kind of assembler from a
> > language
> > to AIC sequencer code). That is, the tool uses db1 (as mkdep.c uses
> > glibc)
> > but once you have generated the sequencer instructions, that is what is
> > built
> > into the kernel, not the tool (aicasm).
> 
> It's very nice... Now one should have not only special kgcc to build the
> kernel, but also the obsolete library with all the development stuff
> installed... Is it sane?
> 

What I dunno is why the h... is needed to rebuild the code everytime you build
a kernel. Just ship the ucode and remove the aicasm subtree from kernel.
Perhaps mrproper makes things too clean, and just should leave there the
sequencer code.

-- 
J.A. Magallon                                                      $> cd pub
mailto:jamagallon@able.es                                          $> more beer

Linux werewolf 2.4.2-ac11 #1 SMP Sat Mar 3 22:18:57 CET 2001 i686


  reply	other threads:[~2001-03-05 23:31 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-05 21:01 Linux 2.4.2ac12 Alan Cox
2001-03-05 21:17 ` Alexander Viro
2001-03-05 22:43   ` Sergey Kubushin
2001-03-05 22:56     ` J . A . Magallon
2001-03-05 23:11       ` Alexander Viro
2001-03-06  2:06         ` Alan Cox
2001-03-06  2:39           ` Alexander Viro
2001-03-05 23:13       ` Sergey Kubushin
2001-03-05 23:30         ` J . A . Magallon [this message]
2001-03-05 23:07     ` Jeff Garzik
2001-03-05 23:21       ` Sergey Kubushin
2001-03-05 23:31         ` Jeff Garzik
2001-03-06  2:04     ` Alan Cox
2001-03-06  2:10       ` Sergey Kubushin
2001-03-06  2:19         ` Alan Cox
2001-03-05 21:37 ` David Riley
2001-03-05 21:48   ` John Silva
2001-03-06  8:14   ` Vojtech Pavlik
  -- strict thread matches above, loose matches on Subject: below --
2001-03-05 21:01 Alan Cox

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=20010306003056.C1136@werewolf.able.es \
    --to=jamagallon@able.es \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=ksi@cyberbills.com \
    --cc=linux-kernel@vger.kernel.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.