From: "Satyam Sharma" <satyam.sharma@gmail.com>
To: "Mike Frysinger" <vapier@gentoo.org>
Cc: linuxsh-dev@lists.sourceforge.net,
"Adrian McMenamin" <adrian@newgolddream.dyndns.info>,
LKML <linux-kernel@vger.kernel.org>,
"Sam Ravnborg" <sam@ravnborg.org>
Subject: sh section mismatches [was Re: 2.6.22-rc6 on Dreamcast (SH4)]
Date: Thu, 28 Jun 2007 17:27:55 +0530 [thread overview]
Message-ID: <a781481a0706280457r4abb5046wc82cff9d49b7975e@mail.gmail.com> (raw)
Hi,
> On Monday 25 June 2007, Adrian McMenamin wrote:
> > Still getting this:
> >
> > MODPOST vmlinux
> > WARNING: arch/sh/boards/dreamcast/built-in.o(.data+0x0): Section
> > mismatch: reference to .init.text: (between 'mv_dreamcast' and
> > 'systemasic_int')
I had sent a patch for this earlier ... Adrian, did you try (build + boot +
testrun) with it? Does this one go away (and system executes fine)?
[ http://lkml.org/lkml/diff/2007/6/23/116/1 ]
[ This has to do with __init functions calling __initmv functions in a
zillion files in arch/sh/boards/.../setup.c which is problematic when
__initmv is not __init itself (!SH_GENERIC && !SH_UNKNOWN) ]
> > WARNING: drivers/built-in.o(.text+0x168e0): Section mismatch: reference
> > to .init.data: (between 'pvr2fb_check_var' and 'pvr2fb_interrupt')
> > WARNING: drivers/built-in.o(.text+0x1701c): Section mismatch: reference
> > to .init.data: (between 'pvr2fb_pci_probe' and 'read_mem')
> > WARNING: drivers/built-in.o(.text+0x17024): Section mismatch: reference
> > to .init.text: (between 'pvr2fb_pci_probe' and 'read_mem')
> > WARNING: drivers/built-in.o(.data+0x738): Section mismatch: reference
> > to .init.text: (between 'board_list' and 'pvr2fb_pci_driver')
> > WARNING: drivers/built-in.o(.data+0x750): Section mismatch: reference
> > to .init.text: (between 'board_list' and 'pvr2fb_pci_driver')
drivers/video/pvr2fb.c is a mess with __init, __initdata, __devinit and
__devinitdata (__exit and __devexit variants for good measure) all being
used and referencing each other freely ... I have no idea what function
should actually be what. Sam normally knows about such things,
adding him to Cc: list.
On 6/28/07, Mike Frysinger <vapier@gentoo.org> wrote:
> it means there is code that is not marked as init making references
> function/data that is marked as init ...
These warnings are most likely bogus (still good to get rid of them,
of course).
BTW, in include/asm-sh/machvec_init.h, __initmv is:
__attribute__((__section__(".machvec.init"))) /* .machvec.init */
But from arch/sh/kernel/vmlinux.ld.S the name of the section is:
__machvec_start = .;
.init.machvec : { *(.init.machvec) } /* .init.machvec */
__machvec_end = .;
Am I obtuse, or is there something weird about this?
Satyam
next reply other threads:[~2007-06-28 11:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-28 11:57 Satyam Sharma [this message]
2007-06-28 18:39 ` Sam Ravnborg
2007-06-30 13:40 ` Adrian McMenamin
2007-06-30 13:58 ` Mike Frysinger
2007-06-30 14:03 ` Adrian McMenamin
2007-06-30 14:20 ` Satyam Sharma
2007-06-30 14:27 ` Adrian McMenamin
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=a781481a0706280457r4abb5046wc82cff9d49b7975e@mail.gmail.com \
--to=satyam.sharma@gmail.com \
--cc=adrian@newgolddream.dyndns.info \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxsh-dev@lists.sourceforge.net \
--cc=sam@ravnborg.org \
--cc=vapier@gentoo.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
all inboxes | Powered by JetHome®