Fix a probable copy/paste error.
Signed-Off-By Luis Correia
Index:
target/linux/ramips/files/arch/mips/include/asm/mach-ralink/rt305x/ralink_soc.h
===
---
target/linux/ramips/files/arch/mips/include/asm/mach-ralink/rt305x
Fix a simple typo
Signed-off-by: Luis Correia
---
Index: package/mac80211/Config.in.rt2x00
===
--- package/mac80211/Config.in.rt2x00 (revision 20623)
+++ package/mac80211/Config.in.rt2x00 (working copy)
@@ -9,7 +9,7
een that the platform does not have an EEPROM, the ralink
crap ap-driver uses a file.
>
> Regards,
> Gabor
btw, i've got a small request, can you make the default image type for
ramips "ramdisk-LZMA' ?
Luis Correia
rt2x00 project admin
__
not have an MCU.
Signed-off-by: Luis Correia
---
--- a/drivers/net/wireless/rt2x00/rt2800lib.c 2010-03-26
18:25:50.0 +
+++ b/drivers/net/wireless/rt2x00/rt2800lib.c 2010-04-01
13:05:18.249747122 +0100
@@ -221,9 +221,9 @@
u32 reg;
/*
-* SOC devices don't
The current defaults for ramips rt305x does not allow the USB
subsystem to be selected/built.
This patch is just a small step in that direction.
(warning: patch may be whitespace/tab broken due to GMail)
Signed-off-by: Luis Correia
---
Index: target/linux/ramips/rt305x/config-2.6.32
Hi Jonas
On Sun, Aug 15, 2010 at 20:38, Jonas Gorski
wrote:
> Hello,
>
> some (more or less) generic comments:
>
> On 14 August 2010 10:39, Luis Correia wrote:
>> (...)
>> --- target/linux/ramips/rt305x/config-2.6.32 (revision 22631)
>> +++ target/
The current defaults for ramips rt305x does not allow the USB
subsystem to be selected/built.
usbcore et al is now built correctly (compile tested only on 2.6.34)
Signed-off-by: Luis Correia
---
Index: target/linux/ramips/rt305x/config-2.6.32
The current defaults for ramips rt305x does not allow the USB
subsystem to be selected/built.
This patch is just a small step in that direction.
Signed-off-by: Luis Correia
---
Index: target/linux/ramips/rt305x/config-2.6.32
t set
>> > > -# CONFIG_USB_ARCH_HAS_HCD is not set
>> > > -# CONFIG_USB_ARCH_HAS_OHCI is not set
>> > > CONFIG_USB_SUPPORT=y
>> > > CONFIG_ZONE_DMA_FLAG=0
>> > > --
>> > > 1.7.2.3
>>
>> --
>> Alexander
>
>
> ___
> openwrt-devel mailing list
> openwrt-devel@lists.openwrt.org
> https://lists.openwrt.org/mailman/listinfo/openwrt-devel
>
>
The way I see it is that USB OTG is kind of a proxy, it load the needed drivers.
In this case:
sbnet: Unknown symbol mii_ethtool_sset (err 0)
usbnet: Unknown symbol mii_link_ok (err 0)
usbnet: Unknown symbol mii_nway_restart (err 0)
usbnet: Unknown symbol mii_ethtool_gset (err 0)
usbnet needs the "mii" driver for some reason, dependancies perhaps :)
Luis Correia
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
ulatory domain for
frequency restrictions.
It could solve your current problem.
But, as always, there may be hundreds of reasons why this approach may
not be possible.
>
> i guess you did something wrong then
> _____
d).
>
> I will be happy to share if anyone is interested.
>
Yes, please share it :)
> Regards,
> Layne
Luis Correia
rt2x00 project admin
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
11 matches
Mail list logo
