From: eric m. <eri...@gm...> - 2008-07-21 02:10:57
|
> Hi Eric, > > I've run into some difficulties. set_pxa_fb_info is: > > void __init set_pxa_fb_info(struct pxafb_mach_info *info) > > and not exported. Therefore am200epd can't be built as a module now > that it depends on set_pxa_fb_info. That is fine, I switched am200epd > to a built-in. But then because set_pxa_fb_info is __init, it > disappears before am200epd is ready to call it. This is because > am200epd needs metronomefb's framebuffer size and info which it only > finds out after full boot into userspace when it gets its firmware > from a udev script. I think this means that I would also need to make > metronomefb a built-in and figure out how to compile in metronome's > firmware. I haven't figured out how to do the latter yet. > I see no reason why set_pxa_fb_info() cannot be exported, though its primary use is in the board setup code. > I started thinking about maybe creating something different, like > maybe set_mod_pxa_fb_info that would work more dynamically (ie: alloc > a platform_device dynamically, thus making it possible for > device_release to work, rather than using a static struct > pxa_device_fb) and allow for module support without requiring any > exports other than itself. Is this something that's of interest or > should I focus on the former? That sounds a bit trickier maybe we should avoid. > > Thanks, > jaya > -- Cheers - eric |