Dave, regarding:
 
Now when you say that changes in printk aren't showing up, were you
just reloading the kernel, or were you also updating the loadable
modules?

I was reloading the kernel.

I don't know how to update the loadable modules.

(this update the loadable modules might take care of message:
ads7846 spi1.0: touchscreen, irq 274

)
Searching for 'Touchscreen as', which are words in one message talking about detection of
devices on SPI, doesn't show in ads7846.c.

The message is:
input: ADS7846 Touchscreen as /devices/platform/omap2_mcspi.1/spi1.0/input/input0
The detection comes first.
The driver is second.

Ion A. Beza.

On Wed, Feb 24, 2010 at 3:49 PM, Dave Hylands <dhylands@gmail.com> wrote:
Hi Tony,

...snip...
> Regarding your own answer Dave, and the slicing of the log of the boot file,
> I consider this:
>
>> The following messages are most likely from loadable kernel modules
>> being loaded as part of the /etc/rc.d mechanism
>>
>> ------------------------------
>>>
>>> ----------------------
>>> > Ion's test 9: SPI clock is enabled here.
>>> > ads7846 spi1.0: touchscreen, irq 274
>>> >
>>> > input: ADS7846 Touchscreen
>>> > as /devices/platform/omap2_mcspi.1/spi1.0/input/input0
>>> > Caching udev devnode
>
> as being the source of the messages.
>
> So the messages don't come from ads7846.c (touchscreen driver), but from:
> "...part of the /etc/rc.d mechanism..."

Well, they're still probably coming from ads7846.c. The ads7846 module
is being loaded by "...part of the /etc/rc.d mechanism..."

What I was really trying to say, is that those messages definitely
didn't come from u-boot as u-boot ended a long time earlier in the
log.

Now when you say that changes in printk aren't showing up, were you
just reloading the kernel, or were you also updating the loadable
modules?

--
Dave Hylands
Shuswap, BC, Canada
http://www.DaveHylands.com/

------------------------------------------------------------------------------
Download Intel&#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
gumstix-users mailing list
gumstix-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/gumstix-users