From: Denys Vlasenko <vda.linux@googlemail.com>
To: Hannes Reinecke <hare@suse.de>
Cc: Andrew Morton <akpm@linux-foundation.org>, linux-scsi@vger.kernel.org
Subject: Re: [PATCH 2/3] debloat aic7xxx and aic79xx drivers
Date: Tue, 8 Apr 2008 17:08:06 +0200 [thread overview]
Message-ID: <200804081708.06787.vda.linux@googlemail.com> (raw)
In-Reply-To: <47FB8713.3030208@suse.de>
On Tuesday 08 April 2008 16:54, Hannes Reinecke wrote:
> Hi Denys,
>
> Denys Vlasenko wrote:
> > On Tuesday 08 April 2008 14:23, Hannes Reinecke wrote:
> [ .. ]
> >> What we have to do here is to modify aicasm to not print out the
> >> unused definitions, and copy those (autogenerated) files over to
> >> the *_shipped files to have them synced properly.
> >> Hand-patching the *_shipped files is not a good idea.
> >
> > I do understand this, and I do understnad then _shipped files
> > are generated. But I failed to find out HOW they are generated.
> > I don't want to _only_ patch aicasm/* files and skip checking
> > that my changes work (or at least compile).
> >
> > Please let me know how to regenerate these _shipped files,
> > and I will fix it "correctly" by modifying aicasm/* files.
>
> CONFIG_PREVENT_FIRMWARE_BUILD is the trick.
> Once it's enable there's a config option which allows you to
> build the aic7xxx firmware files from scratch.
Well, I already tried it, and I mentioned it in my previous email.
Relevant part of make output:
LD kernel/built-in.o
make -C drivers/scsi/aic7xxx/aicasm
bison -d -b aicasm_gram aicasm_gram.y
aicasm_gram.y: warning: 1 useless nonterminal and 6 useless rules
aicasm_gram.y:217.46-54: warning: useless nonterminal: f4_opcode
aicasm_gram.y:1315.9-37: warning: useless rule: f4_opcode: T_OR16
aicasm_gram.y:1316.9-38: warning: useless rule: f4_opcode: T_AND16
aicasm_gram.y:1317.9-38: warning: useless rule: f4_opcode: T_XOR16
aicasm_gram.y:1318.9-38: warning: useless rule: f4_opcode: T_ADD16
aicasm_gram.y:1319.9-38: warning: useless rule: f4_opcode: T_ADC16
aicasm_gram.y:1320.9-38: warning: useless rule: f4_opcode: T_MVI16
mv aicasm_gram.tab.c aicasm_gram.c
mv aicasm_gram.tab.h aicasm_gram.h
bison -d -b aicasm_macro_gram -p mm aicasm_macro_gram.y
mv aicasm_macro_gram.tab.c aicasm_macro_gram.c
mv aicasm_macro_gram.tab.h aicasm_macro_gram.h
flex -oaicasm_scan.c aicasm_scan.l
flex -Pmm -oaicasm_macro_scan.c aicasm_macro_scan.l
gcc -I/usr/include -I. aicasm.c aicasm_symbol.c aicasm_gram.c aicasm_macro_gram.c aicasm_scan.c aicasm_macro_scan.c -o aicasm -ldb
drivers/scsi/aic7xxx/aicasm/aicasm -Idrivers/scsi/aic7xxx -r drivers/scsi/aic7xxx/aic79xx_reg.h \
-p drivers/scsi/aic7xxx/aic79xx_reg_print.c -i aic79xx_osm.h -o drivers/scsi/aic7xxx/aic79xx_seq.h \
drivers/scsi/aic7xxx/aic79xx.seq
drivers/scsi/aic7xxx/aicasm/aicasm: 826 instructions used
CC drivers/scsi/aic7xxx/aic79xx_core.o
CC drivers/scsi/aic7xxx/aic79xx_pci.o
CC drivers/scsi/aic7xxx/aic79xx_reg_print.o
CC drivers/scsi/aic7xxx/aic79xx_osm.o
CC drivers/scsi/aic7xxx/aic79xx_proc.o
CC drivers/scsi/aic7xxx/aic79xx_osm_pci.o
drivers/scsi/aic7xxx/aicasm/aicasm -Idrivers/scsi/aic7xxx -r drivers/scsi/aic7xxx/aic7xxx_reg.h \
-p drivers/scsi/aic7xxx/aic7xxx_reg_print.c -i aic7xxx_osm.h -o drivers/scsi/aic7xxx/aic7xxx_seq.h \
drivers/scsi/aic7xxx/aic7xxx.seq
drivers/scsi/aic7xxx/aicasm/aicasm: 880 instructions used
CC drivers/scsi/aic7xxx/aic7xxx_core.o
> But you need my patch I just posted to linux-scsi, otherwise
> aicasm will complain and not build anything.
Indeed, I found out that _shipped files are not updated
after above.
Can you send this patch to me? I'm not subscribed to linux-scsi...
--
vda
next prev parent reply other threads:[~2008-04-08 15:08 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-23 3:40 [PATCH 0/3] debloat aic7xxx and aic79xx drivers Denys Vlasenko
2008-03-23 3:41 ` [PATCH 1/3] " Denys Vlasenko
2008-03-23 3:42 ` [PATCH 2/3] " Denys Vlasenko
2008-03-23 3:42 ` [PATCH 3/3] " Denys Vlasenko
2008-04-07 10:36 ` Hannes Reinecke
2008-04-07 10:36 ` Hannes Reinecke
2008-04-07 10:34 ` [PATCH 2/3] " Hannes Reinecke
2008-04-07 10:34 ` Hannes Reinecke
2008-04-07 18:00 ` Denys Vlasenko
2008-04-08 12:23 ` Hannes Reinecke
2008-04-08 14:08 ` Denys Vlasenko
2008-04-08 14:54 ` Hannes Reinecke
2008-04-08 15:08 ` Denys Vlasenko [this message]
2008-04-14 18:47 ` Denys Vlasenko
[not found] ` <4804BE68.4000704@suse.de>
2008-04-15 20:10 ` Denys Vlasenko
2008-04-21 5:10 ` Denys Vlasenko
2008-04-14 18:46 ` Denys Vlasenko
2008-04-15 14:44 ` Hannes Reinecke
2008-04-07 10:31 ` [PATCH 1/3] " Hannes Reinecke
2008-04-07 10:31 ` Hannes Reinecke
2008-04-07 18:01 ` Denys Vlasenko
-- strict thread matches above, loose matches on Subject: below --
2007-10-14 14:58 [PATCH 0/3] " Denys Vlasenko
2007-10-14 15:00 ` [PATCH 1/3] " Denys Vlasenko
2007-10-14 15:01 ` [PATCH 2/3] " Denys Vlasenko
2007-08-31 15:13 [PATCH 0/3] " Denys Vlasenko
2007-08-31 15:15 ` [PATCH 1/3] " Denys Vlasenko
2007-08-31 15:16 ` [PATCH 2/3] " Denys Vlasenko
2007-09-24 10:23 ` Hannes Reinecke
2007-09-24 10:23 ` Hannes Reinecke
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=200804081708.06787.vda.linux@googlemail.com \
--to=vda.linux@googlemail.com \
--cc=akpm@linux-foundation.org \
--cc=hare@suse.de \
--cc=linux-scsi@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.