Re: [OpenWrt-Devel] ttl to rs232 on wl500gp
Maybe the voltage regulator LM1086 works better!! I am using the LM7805 and it adds a few noise. -- FMAY On Mon, 2009-02-09 at 11:25 -0200, Felipe Maya wrote: > You have to add the voltage regulator LM7805 to complete your circuit. > > -- > FMAY > > > On Mon, 2009-02-09 at 07:56 -0500, Brian J. Murrell wrote: > > On Mon, 2009-02-09 at 08:14 -0200, Felipe Maya wrote: > > > Follow the next link to do it. It works with ASUS, LINKSYS and etc.: > > > > > > http://www.myopenrouter.com/article/10811/Hacking-Your-NETGEAR-WGR614L-How-To-Install-A-Serial-Port/ > > > > Yeah, I guess that might have been another way to go. But my rs232/ttl > > converter is already on it's way and it was half the price of those > > ttl/usb cables, even if I do have to rummage through my power supply box > > for a 5V supply, should I need it. Would sure like to avoid the > > external power need though, if I can. > > > > b. > > > > ___ > > openwrt-devel mailing list > > openwrt-devel@lists.openwrt.org > > http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel > > ___ > openwrt-devel mailing list > openwrt-devel@lists.openwrt.org > http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel > ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] ttl to rs232 on wl500gp
You have to add the voltage regulator LM7805 to complete your circuit. -- FMAY On Mon, 2009-02-09 at 07:56 -0500, Brian J. Murrell wrote: > On Mon, 2009-02-09 at 08:14 -0200, Felipe Maya wrote: > > Follow the next link to do it. It works with ASUS, LINKSYS and etc.: > > > > http://www.myopenrouter.com/article/10811/Hacking-Your-NETGEAR-WGR614L-How-To-Install-A-Serial-Port/ > > Yeah, I guess that might have been another way to go. But my rs232/ttl > converter is already on it's way and it was half the price of those > ttl/usb cables, even if I do have to rummage through my power supply box > for a 5V supply, should I need it. Would sure like to avoid the > external power need though, if I can. > > b. > > ___ > openwrt-devel mailing list > openwrt-devel@lists.openwrt.org > http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] ttl to rs232 on wl500gp
Follow the next link to do it. It works with ASUS, LINKSYS and etc.: http://www.myopenrouter.com/article/10811/Hacking-Your-NETGEAR-WGR614L-How-To-Install-A-Serial-Port/ -- FMAY On Sun, 2009-02-08 at 22:53 -0500, Brian J. Murrell wrote: > OK. So I need a serial console on my ASUS WL-500G Premium to debug this > kexec problem I'm having. > > Having a peek at > http://wiki.openwrt.org/OpenWrtDocs/Hardware/Asus/WL500GP#head-8c0c5262c5a79f43d67037a30331937a6f7b8628 > it says that the serial output is TTL level. I have a TTL-to-RS232 > converter on order which apparently uses the popular MAX232 chip for its > work. This adaptor (http://fcpcb.ecrater.com/product.php?pid=1750384) > requires an external 3-5V (300 μA) external supply however. > > I notice on the diagram for the serial connector at the first URL I > pasted above that there is a "3.3V_OUT" available. Is this intended to > supply such a converter or is this for something else and I should still > use an external power supply for the above converter? > > I do notice in the photo > (http://wiki.openwrt.org/OpenWrtDocs/Hardware/Asus/WL500GP/IMG_0007) on > that page that the connector wired to that header is using that > "3.3V_OUT" supply. I wonder if he is using it to power such a > converter. > > Cheers, > b. > > ___ > openwrt-devel mailing list > openwrt-devel@lists.openwrt.org > http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] Strange JFFS partition
Something know what is the reason to that one empty data partition (jffs) has 72% used. root@(noname):/# df -h FilesystemSize Used Available Use% Mounted on /dev/root 2.6M 2.6M 0 100% / tmpfs 7.0M 20.0k 7.0M 0% /tmp /dev/mtdblock/4 448.0k324.0k124.0k 72% /jffs It is a SFLASH_ST serial flash type (blocksize 64*1024 size 4194304). WGR614 Why the following JFFS message could appear? root@(noname):/jffs# mkdir k Write of 68 bytes at 0x0005066c failed. returned 0, retlen 136 mkdir: Cannot create directory `k': Input/output error Thanks for any help. Fmay ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] 2.6 kernel and b43 driver
It was not the same thing with wl500gpv2, still conflicted with the B44. The last test was done with the compat-wireless-2008-07-05. Still missing something. [Kernel-2.6.25.9 compat-wireless-2008-07-05] [EMAIL PROTECTED]:/lib/modules/2.6.25.9# insmod ieee80211_crypt.ko [EMAIL PROTECTED]:/lib/modules/2.6.25.9# insmod ieee80211_crypt_ccmp.ko [EMAIL PROTECTED]:/lib/modules/2.6.25.9# insmod ieee80211_crypt_tkip.ko [EMAIL PROTECTED]:/lib/modules/2.6.25.9# insmod ieee80211_crypt_wep.ko [EMAIL PROTECTED]:/lib/modules/2.6.25.9# insmod ieee80211.ko [EMAIL PROTECTED]:/lib/modules/2.6.25.9# insmod cfg80211.ko [EMAIL PROTECTED]:/lib/modules/2.6.25.9# insmod mac80211.ko [EMAIL PROTECTED]:/lib/modules/2.6.25.9# insmod b43.ko <> [Kernel-2.6.23.17 compat-wireless-2008-05-26] PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data. 64 bytes from 192.168.1.1: icmp_seq=9 ttl=100 time=1954 ms 64 bytes from 192.168.1.1: icmp_seq=10 ttl=100 time=955 ms 64 bytes from 192.168.1.1: icmp_seq=11 ttl=100 time=1.35 ms 64 bytes from 192.168.1.1: icmp_seq=24 ttl=100 time=25.3 ms 64 bytes from 192.168.1.1: icmp_seq=37 ttl=100 time=106 ms 64 bytes from 192.168.1.1: icmp_seq=50 ttl=100 time=152 ms 64 bytes from 192.168.1.1: icmp_seq=63 ttl=100 time=227 ms 64 bytes from 192.168.1.1: icmp_seq=76 ttl=100 time=106 ms 64 bytes from 192.168.1.1: icmp_seq=89 ttl=100 time=185 ms 64 bytes from 192.168.1.1: icmp_seq=116 ttl=100 time=4.35 ms 64 bytes from 192.168.1.1: icmp_seq=129 ttl=100 time=4.37 ms 64 bytes from 192.168.1.1: icmp_seq=142 ttl=100 time=4.39 ms [Kernel-2.6.23.17 compat-wireless-2008-07-05] reboots On Sat, 2008-07-05 at 07:45 -0400, Steve Brown wrote: > I cannot reproduce your results. For me, the patch works fine. > > I did the following: > 1. fresh checkout (r 11635) > 2. added patch to patches-2.6.25 > 3. set these options, all others are default: > target system -> 2.6 > target profile -> no wifi > kernel modules -> wireless drivers -> b43 > 4. built > 5. flashed wl-500gp > 6. brought up wlan0 and got: > ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] 2.6 kernel and b43 driver
Hi Steve, I'm happy too with the result, but.. I did the test with the patch that Michael sent (with and without) disabling the function ssb_pcicore_dev_irqvecs_enable following the e-mails, without the same result. (Kernel 2.6.25.9-wl500gpv2). Steve can you verify the modifications of the test, please, I want to reproduce the result. } //else //ssb_pcicore_dev_irqvecs_enable(&sdev->bus->pcicore, sdev); Thanks, Fmay On Fri, 2008-07-04 at 20:33 -0400, Steve Brown wrote: > Forgot the cc's. And to close the thread. > > Michael Buesch wrote: > > On Friday 04 July 2008 21:39:46 Steve Brown wrote: > > > >> Michael Buesch wrote: > >> > >>> On Tuesday 01 July 2008 21:50:43 Steve Brown wrote: > >>> > >>> > It looks like (almost) every other phy register doesn't respond. I put > in a large (200us) delay between accesses with no change in behaviour. > If it is timing, it must be on the pci bus side of the core. > > > >>> Ah this is a minipci card? > >>> Can you try to play with the PCI bus timings that are initialised in > >>> the PCI-core driver of SSB? See the function that initialises the > >>> PCI-core in hostmode. > >>> > >>> > >>> > >> The problem is actually in b44. The ssb_pcicore_dev_irqvecs_enable call > >> in b44_chip_enable at b44.c:1281 is the cause of the problem. It gets > >> called unconditionally, even if the b44 is not on the pci. With it > >> commented out, b43 loads, loads firmware and returns scan results. > >> > >> It crept in sometime after 2.6.23.1. I'm not familiar with b44 and can't > >> offer a fix. > >> > >> I still don't understand how this caused the bus errors. Anybody got an > >> explanation? > >> > > > > So do you have a PCI bus on the system? Is the wireless connected via > > minipci? > > > > > > > > Yeah well. Probably a silicon glitch. We're not supposed > to change the IRQ routing of the PCI core on the board, as the > IRQs on the board are routed through the Mips core. > > Can you try the following patch? > Please try ethernet and wireless. For wireless it's probably OK > to try loading the driver. But I'd prefer if you try to scan the > channels. That would probably be enough to make sure it works correctly. > > I'll immediately submit this for inclusion in mainline, if you report > success. > Thanks for testing. > > > Index: wireless-testing/drivers/ssb/driver_pcicore.c > === > --- wireless-testing.orig/drivers/ssb/driver_pcicore.c2008-06-10 > 13:58:23.0 +0200 > +++ wireless-testing/drivers/ssb/driver_pcicore.c2008-07-04 > 23:16:02.0 +0200 > @@ -537,6 +537,13 @@ int ssb_pcicore_dev_irqvecs_enable(struc > int err = 0; > u32 tmp; > > +if (dev->bus->bustype != SSB_BUSTYPE_PCI) { > +/* This SSB device is not on a PCI host-bus. So the IRQs are > + * not routed through the PCI core. > + * So we must not enable routing through the PCI core. */ > +goto out; > +} > + > if (!pdev) > goto out; > bus = pdev->bus; > > > The bug is fixed! > > The b43 driver now loads, loads firmware and returns scan results. > > Thanks, > > Steve > > ___ > openwrt-devel mailing list > openwrt-devel@lists.openwrt.org > http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] Add ehci host support for BCM5354 USB20 core
cd->regs); err_put_hcd: usb_put_hcd(hcd); err_dev_disable: ssb_device_disable(dev, flags); return err; } EXPORT_SYMBOL_GPL(ssb_ohci_attach); Thanks for any help On Thu, 2008-06-12 at 21:35 -0400, Felipe Maya wrote: > With the Patch submited by Michael Buesch (follow the patch in this > email), and the Steve Brown Patch, Simultaneously USB ports, seems work > fine!! > > good work!!! > > Index: wireless-testing/drivers/ssb/main.c > === > --- wireless-testing.orig/drivers/ssb/main.c2008-05-17 > 18:44:32.0 +0200 > +++ wireless-testing/drivers/ssb/main.c2008-06-12 15:24:04.0 > +0200 > @@ -1165,21 +1165,27 @@ u32 ssb_dma_translation(struct ssb_devic > } > EXPORT_SYMBOL(ssb_dma_translation); > > int ssb_dma_set_mask(struct ssb_device *ssb_dev, u64 mask) > { > struct device *dma_dev = ssb_dev->dma_dev; > +int err = 0; > > #ifdef CONFIG_SSB_PCIHOST > -if (ssb_dev->bus->bustype == SSB_BUSTYPE_PCI) > -return dma_set_mask(dma_dev, mask); > +if (ssb_dev->bus->bustype == SSB_BUSTYPE_PCI) { > +err = pci_set_dma_mask(ssb_dev->bus->host_pci, mask); > +if (err) > +return err; > +err = pci_set_consistent_dma_mask(ssb_dev->bus->host_pci, > mask); > +return err; > +} > #endif > dma_dev->coherent_dma_mask = mask; > dma_dev->dma_mask = &dma_dev->coherent_dma_mask; > > -return 0; > +return err; > } > EXPORT_SYMBOL(ssb_dma_set_mask); > > int ssb_bus_may_powerdown(struct ssb_bus *bus) > { > struct ssb_chipcommon *cc; > > > On Wed, 2008-06-11 at 15:30 -0700, Steve Brown wrote: > > Felipe Maya wrote: > > > The patch works with one USB port, but with two USB simultaneously > > > something wrong happens. > > > > > > I changed the driver_mipscore.c to enable SSB_DEV_USB11_HOST for bcm5354 > > > at this line (208): > > > > > > > > > if (((bus->chip_id == 0x4710) || (bus->chip_id == 0x5354)) && (irq <= > > > 4)) > > > > > > instead > > > > > > if (((bus->chip_id == 0x4710) && (irq <= 4)) > > > > > > > > > and it seems work fine > > > > > > > > > for (irq = 2, i = 0; i < bus->nr_devices; i++) { > > > dev = &(bus->devices[i]); > > > dev->irq = ssb_mips_irq(dev) + 2; > > > switch (dev->id.coreid) { > > > case SSB_DEV_USB11_HOST: > > > /* shouldn't need a separate irq line for > > > non-4710, most of them have a proper > > > * external usb controller on the pci */ > > > if (((bus->chip_id == 0x4710) || (bus->chip_id > > > == 0x5354)) && (irq <= 4)) { > > > set_irq(dev, irq++); > > > break; > > > } > > > /* fallthrough */ > > > case SSB_DEV_PCI: > > > > > > > > > > > > > > What goes wrong? > > Are you using the patch I posted on this list? > > Also, what router is your 5354 in? > > > > This is very puzzling. One of the major changes was to get rid of the > > fake USB11 device. The single USB20 device now gets shared between the > > ehci and ohci drivers. I don't understand how the code in that case even > > got executed. > > > > I just got a wl500gpv2 that has a 5354 and 2 usb ports. As soon as I get > > some headers soldered to it, I'll try both ports and see if I can get it > > to break. > > > > Steve > > > > My time, is my time!! --- a/drivers/usb/host/ehci-ssb.c 2008-06-19 09:53:49.0 -0400 +++ b/usb/host/ehci-ssb.c 2008-06-19 09:54:20.0 -0400 @@ -23,6 +23,8 @@ */ #include +extern int ssb_ohci_attach(struct ssb_device *dev); +extern void ssb_ohci_detach(struct ssb_device *dev); #define SSB_OHCI_TMSLOW_HOSTMODE (1 << 29) @@ -135,14 +137,16 @@ .endpoint_disable = ehci_endpoint_disable, .get_frame_number = ehci_get_frame, - + .hub_status_data = ehci_hub_status_data, .hub_control = ehci_hub_control, +// .hub_irq_enable = ehci_rhsc_enable, #ifdef CONFIG_PM .bus_suspend = ehci_bus_suspend, .b
Re: [OpenWrt-Devel] [PATCH] Add ehci host support for BCM5354 USB20 core
With the Patch submited by Michael Buesch (follow the patch in this email), and the Steve Brown Patch, Simultaneously USB ports, seems work fine!! good work!!! Index: wireless-testing/drivers/ssb/main.c === --- wireless-testing.orig/drivers/ssb/main.c2008-05-17 18:44:32.0 +0200 +++ wireless-testing/drivers/ssb/main.c2008-06-12 15:24:04.0 +0200 @@ -1165,21 +1165,27 @@ u32 ssb_dma_translation(struct ssb_devic } EXPORT_SYMBOL(ssb_dma_translation); int ssb_dma_set_mask(struct ssb_device *ssb_dev, u64 mask) { struct device *dma_dev = ssb_dev->dma_dev; +int err = 0; #ifdef CONFIG_SSB_PCIHOST -if (ssb_dev->bus->bustype == SSB_BUSTYPE_PCI) -return dma_set_mask(dma_dev, mask); +if (ssb_dev->bus->bustype == SSB_BUSTYPE_PCI) { +err = pci_set_dma_mask(ssb_dev->bus->host_pci, mask); +if (err) +return err; +err = pci_set_consistent_dma_mask(ssb_dev->bus->host_pci, mask); +return err; +} #endif dma_dev->coherent_dma_mask = mask; dma_dev->dma_mask = &dma_dev->coherent_dma_mask; -return 0; +return err; } EXPORT_SYMBOL(ssb_dma_set_mask); int ssb_bus_may_powerdown(struct ssb_bus *bus) { struct ssb_chipcommon *cc; On Wed, 2008-06-11 at 15:30 -0700, Steve Brown wrote: > Felipe Maya wrote: > > The patch works with one USB port, but with two USB simultaneously > > something wrong happens. > > > > I changed the driver_mipscore.c to enable SSB_DEV_USB11_HOST for bcm5354 > > at this line (208): > > > > > > if (((bus->chip_id == 0x4710) || (bus->chip_id == 0x5354)) && (irq <= > > 4)) > > > > instead > > > > if (((bus->chip_id == 0x4710) && (irq <= 4)) > > > > > > and it seems work fine > > > > > > for (irq = 2, i = 0; i < bus->nr_devices; i++) { > > dev = &(bus->devices[i]); > > dev->irq = ssb_mips_irq(dev) + 2; > > switch (dev->id.coreid) { > > case SSB_DEV_USB11_HOST: > > /* shouldn't need a separate irq line for > > non-4710, most of them have a proper > > * external usb controller on the pci */ > > if (((bus->chip_id == 0x4710) || (bus->chip_id > > == 0x5354)) && (irq <= 4)) { > > set_irq(dev, irq++); > > break; > > } > > /* fallthrough */ > > case SSB_DEV_PCI: > > > > > > > > > What goes wrong? > Are you using the patch I posted on this list? > Also, what router is your 5354 in? > > This is very puzzling. One of the major changes was to get rid of the > fake USB11 device. The single USB20 device now gets shared between the > ehci and ohci drivers. I don't understand how the code in that case even > got executed. > > I just got a wl500gpv2 that has a 5354 and 2 usb ports. As soon as I get > some headers soldered to it, I'll try both ports and see if I can get it > to break. > > Steve > My time, is my time!! ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] hybrid-wl compilation
Hi, it was my results of the compilation of http://www.broadcom.com/support/802.11/linux_sta.php on openwrt . make[5]: Leaving directory `/opt/openwrt-2.6.25/build_dir/linux-brcm47xx/linux-2.6.25.5' make[4]: Leaving directory `/opt/openwrt-2.6.25/build_dir/linux-brcm47xx/compat-wireless-2008-06-10' make -C "/opt/openwrt-2.6.25/build_dir/linux-brcm47xx/linux-2.6.25.5" CROSS_COMPILE="mipsel-linux-uclibc-" ARCH="mips" PATH="/opt/openwrt-2.6.25/staging_dir/toolchain-mipsel_gcc4.1.2/bin:/opt/openwrt-2.6.25/staging_dir/host/bin:/opt/openwrt-2.6.25/staging_dir/mipsel/host/bin:/opt/openwrt-2.6.23/staging_dir/toolchain-mipsel_gcc4.1.2/bin:/opt/openwrt-2.6.23/staging_dir/host/bin:/opt/openwrt-2.6.23/staging_dir/mipsel/host/bin:/opt/openwrt-2.6.23/staging_dir/toolchain-mipsel_gcc4.1.2/bin:/opt/openwrt-2.6.23/staging_dir/host/bin:/opt/openwrt-2.6.23/staging_dir/mipsel/host/bin::/usr/lib64/ccache:/usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin:/home/devel/bin" SUBDIRS="/opt/openwrt-2.6.25/build_dir/linux-brcm47xx/compat-wireless-2008-06-10/hybrid-wl" modules make[4]: Entering directory `/opt/openwrt-2.6.25/build_dir/linux-brcm47xx/linux-2.6.25.5' LD [M] /opt/openwrt-2.6.25/build_dir/linux-brcm47xx/compat-wireless-2008-06-10/hybrid-wl/wl.o mipsel-linux-uclibc-ld: /opt/openwrt-2.6.25/build_dir/linux-brcm47xx/compat-wireless-2008-06-10/hybrid-wl/lib/wlc_hybrid.o_shipped: Relocations in generic ELF (EM: 3) mipsel-linux-uclibc-ld: /opt/openwrt-2.6.25/build_dir/linux-brcm47xx/compat-wireless-2008-06-10/hybrid-wl/lib/wlc_hybrid.o_shipped: Relocations in generic ELF (EM: 3) mipsel-linux-uclibc-ld: /opt/openwrt-2.6.25/build_dir/linux-brcm47xx/compat-wireless-2008-06-10/hybrid-wl/lib/wlc_hybrid.o_shipped: Relocations in generic ELF (EM: 3) /opt/openwrt-2.6.25/build_dir/linux-brcm47xx/compat-wireless-2008-06-10/hybrid-wl/lib/wlc_hybrid.o_shipped: could not read symbols: File in wrong format make[5]: *** [/opt/openwrt-2.6.25/build_dir/linux-brcm47xx/compat-wireless-2008-06-10/hybrid-wl/wl.o] Error 1 make[4]: *** [_module_/opt/openwrt-2.6.25/build_dir/linux-brcm47xx/compat-wireless-2008-06-10/hybrid-wl] Error 2 make[4]: Leaving directory `/opt/openwrt-2.6.25/build_dir/linux-brcm47xx/linux-2.6.25.5' make[3]: *** [/opt/openwrt-2.6.25/build_dir/linux-brcm47xx/compat-wireless-2008-06-10/.built] Error 2 make[3]: Leaving directory `/opt/openwrt-2.6.25/package/mac80211' make[2]: *** [package/mac80211/compile] Error 2 make[2]: Leaving directory `/opt/openwrt-2.6.25' make[1]: *** [/opt/openwrt-2.6.25/staging_dir/mipsel/stamp/.package_compile] Error 2 make[1]: Leaving directory `/opt/openwrt-2.6.25' make: *** [world] Error 2 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] Add ehci host support for BCM5354 USB20 core
The patch works with one USB port, but with two USB simultaneously something wrong happens. I changed the driver_mipscore.c to enable SSB_DEV_USB11_HOST for bcm5354 at this line (208): if (((bus->chip_id == 0x4710) || (bus->chip_id == 0x5354)) && (irq <= 4)) instead if (((bus->chip_id == 0x4710) && (irq <= 4)) and it seems work fine for (irq = 2, i = 0; i < bus->nr_devices; i++) { dev = &(bus->devices[i]); dev->irq = ssb_mips_irq(dev) + 2; switch (dev->id.coreid) { case SSB_DEV_USB11_HOST: /* shouldn't need a separate irq line for non-4710, most of them have a proper * external usb controller on the pci */ if (((bus->chip_id == 0x4710) || (bus->chip_id == 0x5354)) && (irq <= 4)) { set_irq(dev, irq++); break; } /* fallthrough */ case SSB_DEV_PCI: On Mon, 2008-06-09 at 05:19 -0700, Steve Brown wrote: > Michael Buesch wrote: > > On Monday 09 June 2008 13:48:35 Steve Brown wrote: > > > >> This adds support to ehci-hcd for the ehci host function of the USB20 ssb > >> core in the Broadcom BCM5354. That core implements both ehci and ohci. The > >> support is implemented as a library or extension to the ohci-ssb support > >> in the ohci-hcd driver and is not standalone. The ehci-hcd driver must > >> load before the ohci-hcd driver. > >> > >> Signed-off-by: Steve Brown <[EMAIL PROTECTED]> > >> Cc: Michael Buesch <[EMAIL PROTECTED]> > >> > > > > Do you have commit access to SVN? > > If not, I'll commit it for you. (I assume you tested this patch and it > > works correctly). > > > > > I don't have commit access. > > I've tested both ehci and ohci using the new code as well as built > without ehci and tested that ohci still worked. This was done using the > same file I submitted. As for the build process, selecting ehci selects > ohci. Also, ehci is loaded first. But, you never know. > > Thanks for your help, > > Steve > ___ > openwrt-devel mailing list > openwrt-devel@lists.openwrt.org > http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] usb ehci driver for ssb
Michael Buesch, you are right.. what do you think about this patch? This need: CONFIG_CMDLINE="root=/dev/mtdblock2 rootfstype=squashfs,jffs2 init=/etc/preinit noinitrd console=ttyS0,115200 no_console_suspend irqpoll acpi_noirq" a/drivers/ssb/driver_mipscore.c 2008-05-19 11:09:26.0 -0400 b/drivers/ssb/driver_mipscore.c 2008-06-04 09:19:01.0 -0400 @@ -201,22 +203,23 @@ dev->irq = ssb_mips_irq(dev) + 2; switch (dev->id.coreid) { case SSB_DEV_USB11_HOST: - /* shouldn't need a separate irq line for non-4710, most of them have a proper -* external usb controller on the pci */ - if ((bus->chip_id == 0x4710) && (irq <= 4)) { + case SSB_DEV_USB20_HOST: +/* shouldn't need a separate irq line for non-4710, most of them have a proper + * external usb controller on the pci */ + if (((bus->chip_id == 0x4710) || (bus->chip_id == 0x5354)) && (irq <= 4)) { set_irq(dev, irq++); break; } /* fallthrough */ case SSB_DEV_PCI: case SSB_DEV_ETHERNET: case SSB_DEV_ETHERNET_GBIT: case SSB_DEV_80211: - case SSB_DEV_USB20_HOST: /* These devices get their own IRQ line if available, the rest goes on IRQ0 */ if (irq <= 4) { set_irq(dev, irq++); break; } } } --- /opt/openwrt-2.6.26/build_dir/linux-brcm47xx/linux-2.6.26-rc1-git1/drivers/usb/host/ohci-ssb.c 2008-05-31 23:24:25.0 -0400 +++ drivers/usb/host/ohci-ssb.c 2008-06-04 10:05:30.0 -0400 @@ -60,6 +60,36 @@ return err; } +#ifdef CONFIG_PM +static int ssb_ohci_hcd_suspend(struct usb_hcd *hcd, pm_message_t message) +{ + struct ssb_ohci_device *ohcidev = hcd_to_ssb_ohci(hcd); + struct ohci_hcd *ohci = &ohcidev->ohci; + unsigned long flags; + + spin_lock_irqsave(&ohci->lock, flags); + + ohci_writel(ohci, OHCI_INTR_MIE, &ohci->regs->intrdisable); + ohci_readl(ohci, &ohci->regs->intrdisable); /* commit write */ + + /* make sure snapshot being resumed re-enumerates everything */ + if (message.event == PM_EVENT_PRETHAW) + ohci_usb_reset(ohci); + + clear_bit(HCD_FLAG_HW_ACCESSIBLE, &hcd->flags); + + spin_unlock_irqrestore(&ohci->lock, flags); + return 0; +} + +static int ssb_ohci_hcd_resume(struct usb_hcd *hcd) +{ + set_bit(HCD_FLAG_HW_ACCESSIBLE, &hcd->flags); + usb_hcd_resume_root_hub(hcd); + return 0; +} +#endif /* CONFIG_PM */ + static const struct hc_driver ssb_ohci_hc_driver = { .description= "ssb-usb-ohci", .product_desc = "SSB OHCI Controller", @@ -73,6 +103,11 @@ .stop = ohci_stop, .shutdown = ohci_shutdown, +#ifdef CONFIG_PM + .suspend= ssb_ohci_hcd_suspend, + .resume = ssb_ohci_hcd_resume, +#endif + .urb_enqueue= ohci_urb_enqueue, .urb_dequeue= ohci_urb_dequeue, .endpoint_disable = ohci_endpoint_disable, @@ -81,6 +116,7 @@ .hub_status_data= ohci_hub_status_data, .hub_control= ohci_hub_control, + .hub_irq_enable = ohci_rhsc_enable, #ifdef CONFIG_PM .bus_suspend= ohci_bus_suspend, .bus_resume = ohci_bus_resume, @@ -96,7 +132,6 @@ usb_remove_hcd(hcd); iounmap(hcd->regs); usb_put_hcd(hcd); - ssb_device_disable(dev, 0); } static int ssb_ohci_attach(struct ssb_device *dev) @@ -106,10 +141,73 @@ int err = -ENOMEM; u32 tmp, flags = 0; - if (dev->id.coreid == SSB_DEV_USB11_HOSTDEV) + if (!(ssb_read32(dev, SSB_TMSLOW) & SSB_TMSLOW_RESET)) + goto core_already_enabled; + + /* +* THE FOLLOWING COMMENTS PRESERVED FROM GPL SOURCE RELEASE +* +* The USB core requires a special bit to be set during core +* reset to enable host (OHCI) mode. Resetting the SB core in +* pcibios_enable_device() is a hack for compatibility with +* vanilla usb-ohci so that it does not have to know about +* SB. A driver that wants to use the USB core in device mode +* should know about SB and should reset the bit back to 0 +* after calling pcibios_enable_device(). +*/ + + if (dev->id.coreid == SSB_DEV_USB11_HOSTDEV){ + if (ssb_device_is_enabled(dev)) +goto core_already_enabled; flags |= SSB_OHCI_TMSLOW_HOSTMODE; + ssb_device
Re: [OpenWrt-Devel] [PATCH] usb ehci driver for ssb
The kernel 2.6.26 has these changes and seem to work well Mensagem Original From: "Michael Buesch" <[EMAIL PROTECTED]> To: openwrt-devel@lists.openwrt.org Sent: Ter, Junho 3, 2008 12:22 pm Subject: Re: [OpenWrt-Devel] [PATCH] usb ehci driver for ssb On Monday 02 June 2008 23:30:52 Steve Brown wrote: > This patch adds a ssb ehci driver as well as support for ssb > multifunction cores. > > It is needed to use the ehci function in the BCM5354's USB2 core. > > See https://dev.openwrt.org/ticket/3365 and > http://forum.openwrt.org/viewtopic.php?id=15106&p=2 for reports of > independent testing. > > Signed-off-by: Steve Brown <[EMAIL PROTECTED]> Your changes to the ssb scanning look like a horrible hack. What are you trying to do? The addition of the "nr_cores" variable looks bogus, too. I think this should all be handled in the driver, like b43 does it, too. b43 is also a multifunction device. -- Greetings Michael. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] b43+bcm5354
B43 result in a segmentation fault with compat-wireless-2008-05-31+recently patches. I'm using wl_apsta_mimo.o (broadcom-wl-4.150.10.5.2+fwcutter-011). this patch was applied (only for 2.6.23): --- a/include/linux/unaligned/packed_struct.h 2008-05-19 08:45:16.0 -0400 +++ b/include/linux/unaligned/packed_struct.h 2008-05-31 12:49:21.0 -0400 @@ -2,11 +2,12 @@ #define _LINUX_UNALIGNED_PACKED_STRUCT_H #include - +#include +/* struct __una_u16 { u16 x __attribute__((packed)); }; struct __una_u32 { u32 x __attribute__((packed)); }; struct __una_u64 { u64 x __attribute__((packed)); }; - +*/ static inline u16 __get_unaligned_cpu16(const void *p) { const struct __una_u16 *ptr = (const struct __una_u16 *)p; dmesg: Linux version 2.6.23.17 ([EMAIL PROTECTED]) (gcc version 4.1.2) #37 Mon Jun 2 17:02:20 EDT 2008 CPU revision is: 00029029 ssb: Core 0.0 found: ChipCommon (cc 0x800, rev 0x14, vendor 0x4243) ssb: Core 1.0 found: Fast Ethernet (cc 0x806, rev 0x09, vendor 0x4243) ssb: Core 2.0 found: MIPS 3302 (cc 0x816, rev 0x08, vendor 0x4243) ssb: Core 3.0 found: USB 2.0 Host (cc 0x819, rev 0x02, vendor 0x4243) ssb: Core 3.1 found: USB 1.1 Host (cc 0x817, rev 0x02, vendor 0x4243) ssb: Core 4.0 found: MEMC SDRAM (cc 0x80F, rev 0x04, vendor 0x4243) ssb: Core 5.0 found: IEEE 802.11 (cc 0x812, rev 0x0D, vendor 0x4243) ssb: Core 6.0 found: Roboswitch (cc 0x81C, rev 0x02, vendor 0x4243) ssb: Initializing MIPS core... ssb: set_irq: core 0x0806, irq 2 => 2 ssb: set_irq: core 0x0819, irq 4 => 3 ssb: set_irq: core 0x0817, irq 3 => 3 ssb: set_irq: core 0x0812, irq 0 => 4 ssb: Sonics Silicon Backplane found at address 0x1800 Determined physical RAM map: memory: 0200 @ (usable) Initrd not found or empty - disabling initrd On node 0 totalpages: 8192 Normal zone: 64 pages used for memmap Normal zone: 0 pages reserved Normal zone: 8128 pages, LIFO batch:0 Movable zone: 0 pages used for memmap Built 1 zonelists in Zone order. Total pages: 8128 Kernel command line: root=/dev/mtdblock2 rootfstype=squashfs,jffs2 init=/etc/preinit noinitrd console=ttyS0,115200 Primary instruction cache 16kB, physically tagged, 4-way, linesize 16 bytes. Primary data cache 16kB, 2-way, linesize 16 bytes. Synthesized TLB refill handler (21 instructions). Synthesized TLB load handler fastpath (33 instructions). Synthesized TLB store handler fastpath (33 instructions). Synthesized TLB modify handler fastpath (32 instructions). PID hash table entries: 128 (order: 7, 512 bytes) Using 120.000 MHz high precision timer. console [ttyS0] enabled Dentry cache hash table entries: 4096 (order: 2, 16384 bytes) Inode-cache hash table entries: 2048 (order: 1, 8192 bytes) Memory: 29900k/32768k available (2015k kernel code, 2868k reserved, 288k data, 120k init, 0k highmem) Calibrating delay loop... 239.10 BogoMIPS (lpj=478208) Mount-cache hash table entries: 512 NET: Registered protocol family 16 Time: MIPS clocksource has been installed. NET: Registered protocol family 2 IP route cache hash table entries: 1024 (order: 0, 4096 bytes) TCP established hash table entries: 1024 (order: 1, 8192 bytes) TCP bind hash table entries: 1024 (order: 0, 4096 bytes) TCP: Hash tables configured (established 1024 bind 1024) TCP reno registered detected lzma initramfs initramfs: LZMA lc=1,lp=2,pb=2,origSize=512 squashfs: version 3.0 (2006/03/15) Phillip Lougher Registering mini_fo version $Id$ JFFS2 version 2.2. (NAND) (SUMMARY) © 2001-2006 Red Hat, Inc. io scheduler noop registered io scheduler deadline registered (default) Serial: 8250/16550 driver $Revision: 1.90 $ 2 ports, IRQ sharing enabled serial8250: ttyS0 at MMIO 0x0 (irq = 3) is a 16550A serial8250: ttyS1 at MMIO 0x0 (irq = 3) is a 16550A b44.c:v1.01 (Jun 16, 2006) eth0: Broadcom 10/100BaseT Ethernet 00:1e:8c:ce:f7:d2 flash init: 0x1c00 0x0200 Physically mapped flash: Found 1 x16 devices at 0x0 in 16-bit bank Physically mapped flash: Found an alias at 0x80 for the chip at 0x0 Physically mapped flash: Found an alias at 0x100 for the chip at 0x0 Physically mapped flash: Found an alias at 0x180 for the chip at 0x0 Amd/Fujitsu Extended Query Table at 0x0040 number of CFI chips: 1 cfi_cmdset_0002: Disabling erase-suspend-program due to code brokenness. Flash device: 0x80 at 0x1fc0 bootloader size: 131072 Creating 4 MTD partitions on "Physically mapped flash": 0x-0x0002 : "cfe" 0x0002-0x007f : "linux" 0x000e-0x007f : "rootfs" mtd: partition "rootfs" set to be root filesystem split_squashfs: no squashfs found in "Physically mapped flash" 0x007f-0x0080 : "nvram" nf_conntrack version 0.5.0 (1024 buckets, 4096 max) ip_tables: (C) 2000-2006 Netfilter Core Team TCP vegas registered NET: Registered protocol family 1 NET: Registered protocol family 17 802.1Q VLAN Support v1.8 Ben Greear <[EMAIL PROTECTED]> All bugs added by David S. Miller <[EMAIL PROTECTED]> VFS: Mounted root (jffs2 filesystem) readonly. Freei
[OpenWrt-Devel] compat-wireless unaligned-patch
The follow patch correct the compat-wireless unaligened inconsistency: package/mac80211/patches/001-unaligned.patch --- a/include/linux/unaligned/packed_struct.h 2008-05-19 08:45:16.0 -0400 +++ b/include/linux/unaligned/packed_struct.h 2008-05-31 12:49:21.0 -0400 @@ -2,11 +2,12 @@ #define _LINUX_UNALIGNED_PACKED_STRUCT_H #include - +#include +/* struct __una_u16 { u16 x __attribute__((packed)); }; struct __una_u32 { u32 x __attribute__((packed)); }; struct __una_u64 { u64 x __attribute__((packed)); }; - +*/ static inline u16 __get_unaligned_cpu16(const void *p) { const struct __una_u16 *ptr = (const struct __una_u16 *)p; ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] BCM5354+usb-serial+kernel-2.4.36.4+LOGREAD
[EMAIL PROTECTED]:/# microcom /dev/usb/tts/0 connected to '/dev/usb/tts/0' (9600 bps), exit with ctrl-X... +ZUSIMR:2 Manufacturer: ZTE INCORPORATED Model: MF622 Revision: CLAP671M3V1.0.0B02 CLAP671M3V1.0.0B02 1 [Jan 28 2008 16:00:00] IMEI: 356545014728178 +GCAP: +CGSM,+DS,+ES OK ATI Manufacturer: ZTE INCORPORATED Model: MF622 Revision: CLAP671M3V1.0.0B02 CLAP671M3V1.0.0B02 1 [Jan 28 2008 16:00:00] IMEI: 356545014728178 +GCAP: +CGSM,+DS,+ES OK +ZUSIMR:2 +ZUSIMR:2 <<> LOGREAD: usb-uhci.c: $Revision: 1.275 $ time 16:03:26 May 21 2008 usb-uhci.c: High bandwidth mode enabled usb-uhci.c: v1.275:USB Universal Host Controller Interface driver PCI: Setting latency timer of device 00:03.1 to 64 ehci_hcd 00:03.1: PCI device 14e4:471a ehci_hcd 00:03.1: irq 6, pci mem b8003800 usb.c: new USB bus registered, assigned bus number 1 ehci_hcd 00:03.1: illegal capability! ehci_hcd 00:03.1: USB 0.0 enabled, EHCI 1.00, driver 2003-Dec-29/2.4 hub.c: USB hub found hub.c: 2 ports detected usb.c: registered new driver serial usbserial.c: USB Serial support registered for Generic usbserial.c: USB Serial Driver core v1.4 usbserial.c: USB Serial support registered for PL-2303 HSDPA modem pl2303.c: Prolific PL2303 USB to serial adaptor driver hub.c: new USB device 00:03.1-1, assigned address 2 hub.c: USB hub found hub.c: 2 ports detected hub.c: new USB device 00:03.1-1.1, assigned address 3 usbserial.c: PL-2303 HSDPA modem converter detected KERNEL DEBUG => USBSERIAL.O buffer_size = 4096<7>pl2303.c: device type: 2 usbserial.c: PL-2303 HSDPA modem converter now attached to ttyUSB0 (or usb/tts/0 for devfs) usbserial.c: PL-2303 HSDPA modem converter detected KERNEL DEBUG => USBSERIAL.O buffer_size = 4096<7>pl2303.c: device type: 2 usbserial.c: PL-2303 HSDPA modem converter now attached to ttyUSB1 (or usb/tts/1 for devfs) usbserial.c: PL-2303 HSDPA modem converter detected KERNEL DEBUG => USBSERIAL.O buffer_size = 4096<7>pl2303.c: device type: 2 usbserial.c: PL-2303 HSDPA modem converter now attached to ttyUSB2 (or usb/tts/2 for devfs) [EMAIL PROTECTED]:/# logread | tail Jan 1 00:00:13 OpenWrt user.info kernel: usbserial.c: PL-2303 HSDPA modem converter now attached to ttyUSB2 (or usb/tts/2 for devfs) Jan 1 00:00:15 OpenWrt authpriv.info dropbear[392]: Running in background Jan 1 00:00:19 OpenWrt daemon.info dnsmasq[423]: started, version 2.41 cachesize 150 Jan 1 00:00:19 OpenWrt daemon.info dnsmasq[423]: compile time options: IPv6 GNU-getopt ISC-leasefile no-DBus no-I18N TFTP Jan 1 00:00:19 OpenWrt daemon.info dnsmasq[423]: DHCP, IP range 192.168.1.100 -- 192.168.1.250, lease time 12h Jan 1 00:00:19 OpenWrt daemon.info dnsmasq[423]: using local addresses only for domain lan Jan 1 00:00:19 OpenWrt daemon.warn dnsmasq[423]: failed to access /tmp/resolv.conf.auto: No such file or directory Jan 1 00:00:19 OpenWrt daemon.info dnsmasq[423]: read /etc/hosts - 1 addresses Jan 1 00:00:19 OpenWrt daemon.err dnsmasq[423]: failed to read /etc/ethers:No such file or directory Jan 1 00:00:19 OpenWrt user.info : sysctl: error: 'net.ipv6.conf.all.forwarding' is an unknown key [EMAIL PROTECTED]:/# logread | tail -f Jan 1 00:00:13 OpenWrt user.info kernel: usbserial.c: PL-2303 HSDPA modem converter now attached to ttyUSB2 (or usb/tts/2 for devfs) Jan 1 00:00:15 OpenWrt authpriv.info dropbear[392]: Running in background Jan 1 00:00:19 OpenWrt daemon.info dnsmasq[423]: started, version 2.41 cachesize 150 Jan 1 00:00:19 OpenWrt daemon.info dnsmasq[423]: compile time options: IPv6 GNU-getopt ISC-leasefile no-DBus no-I18N TFTP Jan 1 00:00:19 OpenWrt daemon.info dnsmasq[423]: DHCP, IP range 192.168.1.100 -- 192.168.1.250, lease time 12h Jan 1 00:00:19 OpenWrt daemon.info dnsmasq[423]: using local addresses only for domain lan Jan 1 00:00:19 OpenWrt daemon.warn dnsmasq[423]: failed to access /tmp/resolv.conf.auto: No such file or directory Jan 1 00:00:19 OpenWrt daemon.info dnsmasq[423]: read /etc/hosts - 1 addresses Jan 1 00:00:19 OpenWrt daemon.err dnsmasq[423]: failed to read /etc/ethers:No such file or directory Jan 1 00:00:19 OpenWrt user.info : sysctl: error: 'net.ipv6.conf.all.forwarding' is an unknown key [EMAIL PROTECTED]:/# logread | tail Jan 1 00:01:48 OpenWrt user.debug kernel: pl2303.c: pl2303_write_room - port 0 Jan 1 00:01:48 OpenWrt user.debug kernel: pl2303.c: pl2303_write_room - returns 4095 Jan 1 00:01:48 OpenWrt user.debug kernel: pl2303.c: pl2303_chars_in_buffer - port 0 Jan 1 00:01:48 OpenWrt user.debug kernel: pl2303.c: pl2303_chars_in_buffer - returns 0 Jan 1 00:01:48 OpenWrt user.debug kernel: pl2303.c: pl2303_write_room - port 0 Jan 1 00:01:48 OpenWrt user.debug kernel: pl2303.c: pl2303_write_room - returns 4095 Jan 1 00:01:48 OpenWrt user.debug kernel: pl2303.c: pl2303_chars_in_buffer - port 0 Jan 1 00:01:48 OpenWrt user.debug kernel: pl2303.c: pl2303_chars_in_buffer - returns 0 Jan 1 00:01:48 OpenWrt user.debug kernel: pl2303.c: pl2303_write_room - port 0 Jan 1 00:01:48 OpenWrt user.debug
[OpenWrt-Devel] BCM5354+usb-serial+kernel-2.4.36.4
With relation to the Openwrt with WL500GP-v2 test (BCM5354 chipset), I have obtained a BUG response. After the first secs of the test with usb-serial or pl2303 with microcom, the system reboot. I would like to know if the problem is in the driver (usb-uhci, usb-serial) or if is there some chipset inconsistency with the kernel?. # Miscellaneous USB options # # CONFIG_USB_DEVICEFS is not set # CONFIG_USB_BANDWIDTH is not set # # USB Host Controller Drivers # CONFIG_USB_EHCI_HCD=m CONFIG_USB_UHCI=m CONFIG_USB_UHCI_HIGH_BANDWIDTH=y # CONFIG_USB_UHCI_ALT is not set # CONFIG_USB_OHCI is not set Find some diff files including the option.c (needing some corrections) GSM driver adapted to the kernel 2.4 as follows: diff -uNr --exclude='.*' --exclude='*.o' --exclude='*~' a/drivers/usb/serial/Config.in drivers/usb/serial/Config.in --- a/drivers/usb/serial/Config.in 2008-05-06 19:00:29.0 -0400 +++ b/drivers/usb/serial/Config.in 2008-05-19 18:29:25.0 -0400 @@ -8,6 +8,7 @@ if [ "$CONFIG_USB_SERIAL" != "n" ]; then dep_bool ' USB Serial Converter verbose debug' CONFIG_USB_SERIAL_DEBUG $CONFIG_USB_SERIAL dep_mbool ' USB Generic Serial Driver' CONFIG_USB_SERIAL_GENERIC $CONFIG_USB_SERIAL + dep_tristate ' USB 3G MODEM' CONFIG_USB_SERIAL_OPTION $CONFIG_USB_SERIAL dep_tristate ' USB Belkin and Peracom Single Port Serial Driver' CONFIG_USB_SERIAL_BELKIN $CONFIG_USB_SERIAL dep_tristate ' USB ConnectTech WhiteHEAT Serial Driver' CONFIG_USB_SERIAL_WHITEHEAT $CONFIG_USB_SERIAL dep_tristate ' USB Digi International AccelePort USB Serial Driver' CONFIG_USB_SERIAL_DIGI_ACCELEPORT $CONFIG_USB_SERIAL diff -uNr --exclude='.*' --exclude='*.o' --exclude='*~' a/drivers/usb/serial/Makefile drivers/usb/serial/Makefile --- a/drivers/usb/serial/Makefile 2008-05-06 19:00:29.0 -0400 +++ b/drivers/usb/serial/Makefile 2008-05-22 14:29:13.0 -0400 @@ -26,7 +26,7 @@ obj-$(CONFIG_USB_SERIAL_IR)+= ir-usb.o obj-$(CONFIG_USB_SERIAL_KLSI) += kl5kusb105.o obj-$(CONFIG_USB_SERIAL_KOBIL_SCT) += kobil_sct.o - +obj-$(CONFIG_USB_SERIAL_OPTION) += option.o # Objects that export symbols. export-objs:= usbserial.o diff -uNr --exclude='.*' --exclude='*.o' --exclude='*~' a/drivers/usb/serial/option.c drivers/usb/serial/option.c --- a/drivers/usb/serial/option.c 1969-12-31 19:00:00.0 -0500 +++ b/drivers/usb/serial/option.c 2008-05-22 14:22:06.0 -0400 @@ -0,0 +1,840 @@ +/* + USB Driver for GSM modems + + Copyright (C) 2005 Matthias Urlichs <[EMAIL PROTECTED]> + + This driver is free software; you can redistribute it and/or modify + it under the terms of Version 2 of the GNU General Public License as + published by the Free Software Foundation. + + Portions copied from the Keyspan driver by Hugh Blemings <[EMAIL PROTECTED]> + + History: see the git log. + + Work sponsored by: Sigos GmbH, Germany <[EMAIL PROTECTED]> + + This driver exists because the "normal" serial driver doesn't work too well + with GSM modems. Issues: + - data loss -- one single Receive URB is not nearly enough + - nonstandard flow (Option devices) control + - controlling the baud rate doesn't make sense + + This driver is named "option" because the most common device it's + used for is a PC-Card (with an internal OHCI-USB interface, behind + which the GSM interface sits), made by Option Inc. + + Some of the "one port" devices actually exhibit multiple USB instances + on the USB bus. This is not a bug, these ports are used for different + device features. + + Kernel 2.4.36.4 (2008), Felipe Maya <[EMAIL PROTECTED]> + +*/ + +#define DRIVER_VERSION "v0.7.1" +#define DRIVER_AUTHOR "Matthias Urlichs <[EMAIL PROTECTED]>" +#define DRIVER_DESC "USB Driver for GSM modems" + +#include +#include +#include +#include +#include +#include +#include +#include +#include +#include +#include +#include +#include + +#ifdef CONFIG_USB_SERIAL_DEBUG + static int debug = 1; +#else + static int debug; +#endif + +#include "usb-serial.h" + + + +/* Function prototypes */ +static int option_open(struct usb_serial_port *port, struct file *filp); +static void option_close(struct usb_serial_port *port, struct file *filp); +static int option_startup(struct usb_serial *serial); +static void option_shutdown(struct usb_serial *serial); +static void option_rx_throttle(struct usb_serial_port *port); +static void option_rx_unthrottle(struct usb_serial_port *port); +static int option_write_room(struct usb_serial_port *port); + +static void option_instat_callback(struct urb *urb); + +static int option_write(struct
Re: [OpenWrt-Devel] brcm47xx 2.6 still does not compile
the compilation is succeded for me, but eth doesn't respond for any ping. (BCM5354 WL500GPV2) CONFIG_B44=y CONFIG_B44_PCI_AUTOSELECT=y CONFIG_B44_PCICORE_AUTOSELECT=y CONFIG_B44_PCI=y Mensagem Original From: "Peter Denison" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED], "OpenWrt Development List" Sent: Ter, Maio 20, 2008 5:23 am Subject: Re: [OpenWrt-Devel] brcm47xx 2.6 still does not compile On Mon, 19 May 2008, Steve Brown wrote: > Dirk Nehring wrote: >> [...] >> make[5]: Leaving directory `/home/technik/dnehring/openwrt/build_dir/linux-brcm47xx/linux-2.6.25.1' >> make[5]: Entering directory `/home/technik/dnehring/openwrt/build_dir/linux-brcm47xx/linux-2.6.25.1' >> CHK include/linux/version.h >> CHK include/linux/utsrelease.h >> CALLscripts/checksyscalls.sh >> CHK include/linux/compile.h >> CC drivers/ssb/driver_pcicore.o >> drivers/ssb/driver_pcicore.c: In function 'ssb_pcicore_fixup_pcibridge': >> drivers/ssb/driver_pcicore.c:314: error: implicit declaration of function 'pcibios_enable_device' >> make[7]: *** [drivers/ssb/driver_pcicore.o] Error 1 >> make[6]: *** [drivers/ssb] Error 2 >> make[5]: *** [drivers] Error 2 >> make[5]: Leaving directory `/home/technik/dnehring/openwrt/build_dir/linux-brcm47xx/linux-2.6.25.1' >> make[4]: *** [/home/technik/dnehring/openwrt/build_dir/linux-brcm47xx/linux-2.6.25.1/.image] Error 2 >> make[4]: Leaving directory `/home/technik/dnehring/openwrt/target/linux/brcm47xx' >> >> And, iproute2 must be updated (works with iproute2-2.6.25.tar.bz2). Yes. I have a patch waiting to go in, but I'm waiting for confirmation (or time to test it) that it works under older kernels as well. >> > I added the following to config-2.6.25. > > CONFIG_PCI=y > CONFIG_SYS_HAS_EARLY_PRINTK=y > CONFIG_EARLY_PRINTK=y > # CONFIG_MEMSTICK is not set > # CONFIG_SGI_IP28 is not set > # CONFIG_THERMAL is not set > > The config_pci is to get the declaration for pcibios_enable_device to be > included. A better solution would be to add the missing ifdef around > that code. Not really. The platform has PCI, so that config setting should be set. Possibly there are some config dependencies that should go in so that you don't get a compilation failure. > I was pretty surprised at having to add the commented lines. If they > aren't there, you get questions from the 'make oldconfig' during the > kernel build. Sorry. If I understood exactly where to set things to get the right resultant .config, it would work more often. > The early printk stuff was to try to figure why it would boot on a > Buffalo whr-hp-54g, but not an Asus wl520gu. I still don't know why. CONFIG_BCM47XX sets CONFIG_SYS_HAS_EARLY_PRINTK, so you shouldn't need to set that. I can't work out where CONFIG_EARLY_PRINTK is set in my config, maybe by hand? That should probably go in. -- Peter Denison ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] CONFIG_IMQ
Is the CONFIG_IMQ .config kernel parameter necessary in the BCM47xx compilation? ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH 1/2] kernel: allow kernel modules tohave a configuration definition
make menuconfig result as follow: Collecting target info: target/linux/rdcERROR: please fix target/linux/rdc/Makefile Collecting target info: target/linux/rb532ERROR: please fix target/linux/rb532/Makefile Collecting target info: target/linux/amazonERROR: please fix target/linux/amazon/Makefile Collecting target info: target/linux/ar7ERROR: please fix target/linux/ar7/Makefile Collecting target info: target/linux/x86ERROR: please fix target/linux/x86/Makefile Collecting target info: target/linux/iop32xERROR: please fix target/linux/iop32x/Makefile Collecting target info: target/linux/au1000ERROR: please fix target/linux/au1000/Makefile Collecting target info: target/linux/umlERROR: please fix target/linux/uml/Makefile Collecting target info: target/linux/atherosERROR: please fix target/linux/atheros/Makefile Collecting target info: target/linux/etraxERROR: please fix target/linux/etrax/Makefile Collecting target info: target/linux/brcm63xxERROR: please fix target/linux/brcm63xx/Makefile Collecting target info: target/linux/avr32ERROR: please fix target/linux/avr32/Makefile Collecting target info: target/linux/at91ERROR: please fix target/linux/at91/Makefile Collecting target info: target/linux/stormERROR: please fix target/linux/storm/Makefile Collecting target info: target/linux/magicboxERROR: please fix target/linux/magicbox/Makefile Collecting target info: target/linux/adm5120ERROR: please fix target/linux/adm5120/Makefile Collecting target info: target/linux/olpcERROR: please fix target/linux/olpc/Makefile Collecting target info: target/linux/ppc44xERROR: please fix target/linux/ppc44x/Makefile Collecting target info: target/linux/pxaERROR: please fix target/linux/pxa/Makefile Collecting target info: target/linux/brcm-2.4ERROR: please fix target/linux/brcm-2.4/Makefile Collecting target info: target/linux/ifxmipsERROR: please fix target/linux/ifxmips/Makefile Collecting target info: target/linux/sibyteERROR: please fix target/linux/sibyte/Makefile Collecting target info: target/linux/ppc40xERROR: please fix target/linux/ppc40x/Makefile Collecting target info: target/linux/brcm47xxERROR: please fix target/linux/brcm47xx/Makefile Collecting target info: target/linux/ps3ERROR: please fix target/linux/ps3/Makefile Collecting target info: target/linux/ixp4xxERROR: please fix target/linux/ixp4xx/Makefile Collecting target info: done tmp/.config-target.in:1:warning: config symbol defined without type tmp/.config-target.in:8:warning: config symbol defined without type tmp/.config-target.in:13:warning: config symbol defined without type # # using defaults found in .config # Your configuration changes were NOT saved. Mensagem Original From: "Travis Kemen" <[EMAIL PROTECTED]> To: "OpenWrt Development List" Sent: Qua, Maio 14, 2008 9:58 pm Subject: Re: [OpenWrt-Devel] [PATCH 1/2] kernel: allow kernel modules tohave a configuration definition Axel Gembe wrote: > This patch makes kernel modules check if config is defined and creates a config > passthrough target which will evaluate the original config in the generated > package. This is done so kernel modules can have configuration menus like > busybox, etc... > > Signed-off-by: Axel Gembe <[EMAIL PROTECTED]> > --- > include/kernel.mk |6 ++ > 1 files changed, 6 insertions(+), 0 deletions(-) > > diff --git a/include/kernel.mk b/include/kernel.mk > index 52355dc..6d03683 100644 > --- a/include/kernel.mk > +++ b/include/kernel.mk > @@ -120,6 +120,12 @@ $(call KernelPackage/$(1)/description) > endef >endif > > + ifdef KernelPackage/$(1)/config > +define Package/kmod-$(1)/config > +$(call KernelPackage/$(1)/config) > +endef > + endif > + >ifneq ($(if $(KCONFIG),$(filter m,$(foreach c,$(filter-out %=y %=n %=m,$(KCONFIG)),$($(c,.),) > ifneq ($(strip $(FILES)),) >define Package/kmod-$(1)/install Committed r11139. Thanks Travis ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] wl500gp v2 + HUAWEI E226
I install the kernel 2.4.36.4, worked quite well. Already the USB port using the HSDPA modem E226 presents an inconsistency, and that after a certain period of time the system restarts (Reboot). the best configuration of modules in openwrt was: kmod-usb-core, kmod-usb-serial, kmod-usb-uhci, kmod-usb-uhci-iv, kmod-USB2, kmod-usb-acm, kmod-usb-storage, kmod-fs-vfat, kmod - Nozomi, kmod-dpi, kmod-mppe, kmod-dpi-synctty. The module kmod-ohci caused an inconsistency. Another effort was the use of driver pl2303 with compatibility with this modem, working the same way. People, something Idea diff -rc --exclude='*.o' --exclude='.*' /opt/openwrt-2.4.36.4/build_dir/toolchain-mipsel_gcc3.4.6/linux-2.4.36.4/drivers/usb/serial/pl2303.c /opt/openwrt-2.4.36.4/build_dir/linux-brcm-2.4/linux-2.4.36.4/drivers/usb/serial/pl2303.c *** /opt/openwrt-2.4.36.4/build_dir/toolchain-mipsel_gcc3.4.6/linux-2.4.36.4/drivers/usb/serial/pl2303.c2008-05-06 19:00:29.0 -0400 --- /opt/openwrt-2.4.36.4/build_dir/linux-brcm-2.4/linux-2.4.36.4/drivers/usb/serial/pl2303.c 2008-05-12 10:16:05.0 -0400 *** *** 115,120 --- 115,121 { USB_DEVICE(DATAPILOT_U2_VENDOR_ID, DATAPILOT_U2_PRODUCT_ID) }, { USB_DEVICE(BELKIN_VENDOR_ID, BELKIN_PRODUCT_ID) }, { USB_DEVICE(ALCOR_VENDOR_ID, ALCOR_PRODUCT_ID) }, + { USB_DEVICE(HUAWEI_VENDOR_ID, HUAWEI_PRODUCT_ID) }, { USB_DEVICE(WS002IN_VENDOR_ID, WS002IN_PRODUCT_ID) }, { USB_DEVICE(COREGA_VENDOR_ID, COREGA_PRODUCT_ID) }, { USB_DEVICE(HL340_VENDOR_ID, HL340_PRODUCT_ID) }, diff -rc --exclude='*.o' --exclude='.*' /opt/openwrt-2.4.36.4/build_dir/toolchain-mipsel_gcc3.4.6/linux-2.4.36.4/drivers/usb/serial/pl2303.h /opt/openwrt-2.4.36.4/build_dir/linux-brcm-2.4/linux-2.4.36.4/drivers/usb/serial/pl2303.h *** /opt/openwrt-2.4.36.4/build_dir/toolchain-mipsel_gcc3.4.6/linux-2.4.36.4/drivers/usb/serial/pl2303.h2008-05-06 19:00:29.0 -0400 --- /opt/openwrt-2.4.36.4/build_dir/linux-brcm-2.4/linux-2.4.36.4/drivers/usb/serial/pl2303.h 2008-05-12 10:16:47.0 -0400 *** *** 112,114 --- 112,118 /* Y.C. Cable U.S.A., Inc - USB to RS-232 */ #define YCCABLE_VENDOR_ID 0x05ad #define YCCABLE_PRODUCT_ID 0x0fba + + /* Huawei E626 UMTS/HSDPA card (ID: 12d1:1001) --fmay*/ + #define HUAWEI_VENDOR_ID 0x12d1 + #define HUAWEI_PRODUCT_ID 0x1003 diff -rc --exclude='*.o' --exclude='.*' /opt/openwrt-2.4.36.4/build_dir/toolchain-mipsel_gcc3.4.6/linux-2.4.36.4/drivers/usb/serial/usbserial.c /opt/openwrt-2.4.36.4/build_dir/linux-brcm-2.4/linux-2.4.36.4/drivers/usb/serial/usbserial.c *** /opt/openwrt-2.4.36.4/build_dir/toolchain-mipsel_gcc3.4.6/linux-2.4.36.4/drivers/usb/serial/usbserial.c 2008-05-07 23:41:06.0 -0400 --- /opt/openwrt-2.4.36.4/build_dir/linux-brcm-2.4/linux-2.4.36.4/drivers/usb/serial/usbserial.c 2008-05-12 10:17:44.0 -0400 *** *** 1558,1568 --- 1558,1572 err("No free urbs available"); goto probe_error; } + /FMAY HSDPA adaptation #ifdef CONFIG_USB_SERIAL_GENERIC buffer_size = (endpoint->wMaxPacketSize > maxSize) ? endpoint->wMaxPacketSize : maxSize; + /FMAY HSDPA adaptation + buffer_size = (serial->vendor==0x12d1 && serial->product==0x1003) ? 4096 : buffer_size; #else buffer_size = endpoint->wMaxPacketSize; #endif + printk("KERNEL DEBUG => USBSERIAL.O buffer_size = %d", buffer_size); port->bulk_in_endpointAddress = endpoint->bEndpointAddress; port->bulk_in_buffer = kmalloc (buffer_size, GFP_KERNEL); if (!port->bulk_in_buffer) { *** *** 1864,1869 --- 1868,1877 generic_device_ids[7].idVendor = 0x1410; generic_device_ids[7].idProduct = 0x1430; generic_device_ids[7].match_flags = USB_DEVICE_ID_MATCH_VENDOR | USB_DEVICE_ID_MATCH_PRODUCT; + /* Huawei E226 *///FMAY + generic_device_ids[8].idVendor = 0x12d1; + generic_device_ids[8].idProduct = 0x1003; + generic_device_ids[8].match_flags = USB_DEVICE_ID_MATCH_VENDOR | USB_DEVICE_ID_MATCH_PRODUCT; /* register our generic driver with ourselves */ usb_serial_register (&generic_device); #endif diff -rc --exclude='*.o' --exclude='.*' /opt/openwrt-2.4.36.4/build_dir/toolchain-mipsel_gcc3.4.6/linux-2.4.36.4/drivers/usb/storage/initializers.c /opt/openwrt-2.4.36.4/build_dir/linux-brcm-2.4/linux-2.4.36.4/drivers/usb/storage/initializers.c *** /opt/openwrt-2.4.36.4/build_dir/toolchain-mipsel_gcc3.4.6/linux-2.4.36.4/drivers/usb/storage/initializers.c 2008-05-06 19:00:29.0 -0400 --- /opt/openwrt-2.4.36.4/build_dir/linux-brcm-2.4/linux-2.4.36.4/drivers/usb/storage/initializers.c 2008-05-12 09:57:20.0 -0400 *** *** 41,46 --- 41,60 #include "debug.h" #include "transport.h" + /* This places the HUAWEI E226 devices in multi-port mode --fmay*/ + int usb_stor_huawei_e226_init(struct us_data *us) + { + unsigned char data = 0x1; + int result; + + result = usb_stor_control_msg(us, usb_sndctrlpipe(us->pusb_dev, 0), + USB_REQ_SET_FEATURE, + USB_TYPE_STANDARD | USB_RECIP_DEVICE, + 0x01, 0x0, &d
Re: [OpenWrt-Devel] Why oh why...
e-mail to [EMAIL PROTECTED] Mensagem Original From: "David Boreham" <[EMAIL PROTECTED]> To: "OpenWrt Development List" Sent: Qua, Abril 30, 2008 8:39 pm Subject: [OpenWrt-Devel] Why oh why... ...do we have such a big mess of patches for madwifi ? I'm just sayin... every time we pick up a new madwifi revision most of the patches need to be re-done. Has anyone tried to put, for example, the stuff that disables debug code, and the multi-binary stuff back into the upstream code ? Just seems like a strange way to make software (imho) to be spinning on these patches constantly, or alternatively failing to pick up new madwifi revisions because it's too much work to sync up. Patches that are actual bug fixes, not already in the upstream are a fine thing of course. They can be dropped as they are incorporated into madwifi. I'd be happy to work on this. Anyone tried to attack this issue already ? ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel