From: "Simon Holm Thøgersen" <odie@cs.aau.dk>
To: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Cc: "Gao, Yunpeng" <yunpeng.gao@intel.com>,
"linux-ia64@vger.kernel.org" <linux-ia64@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: how to fix nand driver build breakage
Date: Mon, 19 Jan 2009 11:46:18 +0000 [thread overview]
Message-ID: <1232365578.5764.4.camel@odie.local> (raw)
In-Reply-To: <20090120132317.B0B3.KOSAKI.MOTOHIRO@jp.fujitsu.com>
man, 19 01 2009 kl. 13:25 +0900, skrev KOSAKI Motohiro:
> > Hi all,
> >
> > I have to use 64bit variable in my 2.6.27 kernel NAND driver as below:
> > ---------------------------------------------------------------------------
> > u64 NAND_capacity;
> > unsigned int block_num, block_size;
> > ...
> > block_num = NAND_capacity / block_size;
> > ---------------------------------------------------------------------------
> > but it failed when compiling and reports 'undefined reference to `__udivdi3'.
> >
> > Does any idea about this? I need to include some special head file or change something in Kconfig?
> >
> > BTW, the environment is Fedora Core 9, gcc 4.3.0.
>
> Couldn't you use do_div()?
Perhaps rather div_u64, but otherwise he should be able to yes.
Simon Holm Th√∏gersen
--
To unsubscribe from this list: send the line "unsubscribe linux-ia64" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2009-01-19 11:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <38D9F46DFF92C54980D2F2C1E8EE31301FC5E7FB@pdsmsx503.ccr.corp.intel.com>
2009-01-19 4:25 ` how to fix nand driver build breakage KOSAKI Motohiro
2009-01-19 11:46 ` Simon Holm Thøgersen [this message]
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=1232365578.5764.4.camel@odie.local \
--to=odie@cs.aau.dk \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=yunpeng.gao@intel.com \
/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