Weird, but my grep results are different:
$ grep zippy2 * -r
arch/arm/mach-omap2/board-omap3beagle.c:static struct spi_board_info
omap3beagle_zippy2_spi_board_info[] __initdata = {
arch/arm/mach-omap2/board-omap3beagle.c:
omap3beagle_zippy2_spi_board_info[0].irq =
OMAP_GPIO_IRQ(OMAP3BEAGLE_GPIO_KS8851_IRQ);
arch/arm/mach-omap2/board-omap3beagle.c:
set_irq_type(omap3beagle_zippy2_spi_board_info[0].irq,
IRQ_TYPE_EDGE_FALLING);
arch/arm/mach-omap2/board-omap3beagle.c:
spi_register_board_info(omap3beagle_zippy2_spi_board_info,
arch/arm/mach-omap2/board-omap3beagle.c:
ARRAY_SIZE(omap3beagle_zippy2_spi_board_info));
arch/arm/mach-omap2/board-omap3beagle.c: if(!strcmp(expansionboard_name,
"zippy") || !strcmp(expansionboard_name, "zippy2"))
arch/arm/mach-omap2/board-omap3beagle.c: printk(KERN_INFO "Beagle
expansionboard: registering i2c2 bus for zippy/zippy2\n");
arch/arm/mach-omap2/board-omap3beagle.c: if(!strcmp(expansionboard_name,
"zippy2"))
2011/2/9 David Stark <[email protected]>
> I couldn't get MMC2 ( the second MMC slot ) working in Linux until I passed
> "buddy=zippy2" to the kernel command line. Now it works like a charm.
> However, I don't find anything relevant when I grep the kernel source tree
> for "zippy". board-omap3beagle.c only defines one mmc device:
>
> static struct omap2_hsmmc_info mmc[] = {
> {
> .mmc = 1,
> .caps = MMC_CAP_4_BIT_DATA | MMC_CAP_8_BIT_DATA,
> .gpio_wp = 29,
> },
> {} /* Terminator */
> };
>
> So I must either have the wrong source tree, or there is something in an
> init script someplace. Does anyone know how this works?
> _______________________________________________
> Angstrom-distro-users mailing list
> [email protected]
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-users
>
_______________________________________________
Angstrom-distro-users mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-users
