Hello Miguel, On Wednesday 15 September 2010 14:37:38 Miguel GAIO wrote: > Hi Florian > > On Wed, 2010-09-15 at 09:39 +0200, Florian Fainelli wrote: > > Hi Miguel, Daniel, > > > > For your information, I have managed to recently get those changes > > mainline: > > > > - bcm963xx mtd partition parser [1] > > - bcm63xx watchdog driver (not yet pushed) > > > > I will ask Maxime to push the OHCI and EHCI usb drivers mainline, so > > after that the only patches that we have in OpenWrt are: > > > > - 070_bcm63xx_enet_vlan_incoming_fixed.patch: according to Maxime, this > > patch is not exactly valid, and the issue is somewhere else, Daniel, if > > you want to work this out with him > > - 100-reset_buttons.patch: depends on the gpio-buttons driver to be > > merged - 110-gpiodev.patch: useless, /sys/class/gpio/ allows the same > > kind of usage - 140-new_bcm96348gw_leds.patch: needs to be integrated > > with the proper board id fixup patch from Jonas Gorski [2] > > - 150-alice_gate2_leds.patch: ok > > - 170-board_livebox.patch: not complete, so to be kept until ready > > - 180-udc_preliminary_support.patch: no objections pushing it, although > > there are no users of it > > Some NB4 has UDC device. I can make some tests on it.
>From my reading of the bcmusb driver, it is really RNDIS specific and cannot >be used as a true usb gadget driver which could allow other cool features to be implemented (like storage, ethernet ...). > > > - 200-extended-platform-devices.patch: ok > > - 211-nxp-74hc164-gpio-chip-driver.patch: needs to become a SPI driver > > after [3] > > Sure, I will rewrite this part. Thank you, the idea from David Brownell (who commented on the driver), was that this driver should be implemented as a spi driver with the NO_RX flags, and you would need to use spi-gpio to talk to the 74x164 driver. > > > - 220-board-D4PW.patch: ok > > - 221-board-NB4.patch: ok, after nxp-74hc164 has been merged or reworked > > - 240-spi.patch: needs some rework > > I CC Tanguy for this part. He had fixed spi driver to get it working on > NB4. Maybe others tests are needed. I let Tanguy push its fixes to > openwrt. Ok, that's cool, I have some pending fixes on my side for BCM6338. > > > - 250-6358-enet1-external-mii-clk.patch: needs testing on other BCM6358 > > boards > > This fix should be safe for all 6358. But sure needs testing. Ok. > > > - 260-no_ehci_over_current_check.patch: not required, over current > > checking can be turned off by module parameter (so actually we can patch > > the ehci driver to turn it off by default without supplying the module > > parameter) > > > > [1]:http://git.infradead.org/users/dedekind/l2- > > mtd-2.6.git/commit/eafa90853c493d4b6b556286d2ccd38c59d1985e > > [2]: > > https://lists.openwrt.org/pipermail/openwrt-devel/2010-June/007375.html > > [3]: http://lkml.org/lkml/2010/9/1/82 > > Miguel _______________________________________________ openwrt-devel mailing list [email protected] https://lists.openwrt.org/mailman/listinfo/openwrt-devel
