From: mike <mikelee@avantwave.com>
To: linux-mtd@lists.infradead.org
Subject: patching cvs mtd to linux 2.4.27-vsr1
Date: Wed, 01 Dec 2004 15:58:41 +0800 [thread overview]
Message-ID: <41AD79B1.4050303@avantwave.com> (raw)
Dear all
Thanks for helping
I have some problem when patching cvs mtd to linux 2.4.27-vsr1.
after i use the patches/patchin.sh -c -j /usr/src/linux. I compile
kernel as usual practise. But i found that error below.
arm-linux-gcc -D__KERNEL__ -I/usr/src/linux-2.4.27-vrs1/include -Wall
-Wstrict-prototypes -Wno-trigraphs -Os -fno-strict-aliasing -fno-common
-Uarm -fno-common -pipe -mapcs-32 -D__LINUX_ARM_ARCH__=4 -march=armv4
-mshort-load-bytes -msoft-float -Uarm -nostdinc -iwithprefix include
-DKBUILD_BASENAME=chipreg -c -o chipreg.o chipreg.c
In file included from chipreg.c:14:
*/usr/src/linux-2.4.27-vrs1/include/linux/mtd/map.h:127:2: #error "No
bus width supported. What's the point?"
*I check that there is not define of the map_bankwidth on anywhere of
the kernel source. Am i patch wrong kernel version?
Best regard
Mike,Lee
next reply other threads:[~2004-12-01 7:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-01 7:58 mike [this message]
2004-12-01 9:46 ` patching cvs mtd to linux 2.4.27-vsr1 David Woodhouse
2004-12-01 23:32 ` Aras Vaichas
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=41AD79B1.4050303@avantwave.com \
--to=mikelee@avantwave.com \
--cc=linux-mtd@lists.infradead.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