See example of case use in arv4518 patch
Thanks.
2010/11/24 John Crispin
> ok, can you send a patch in that case that makes use of the new pci hook
> please so we can apply the patch + a use case
> ___
> openwrt-devel mailing list
> openwrt-devel@lis
split mach-arv4518 from mach-arv45xx. fix leds. include support for ath5k
wireless driver
Index: target/linux/ifxmips/files/arch/mips/ifxmips/danube/Kconfig
===
--- target/linux/ifxmips/files/arch/mips/ifxmips/danube/Kconfig (revision
add missing support for gpio buttons
Index: target/linux/ifxmips/files/arch/mips/ifxmips/common/devices.c
===
--- target/linux/ifxmips/files/arch/mips/ifxmips/common/devices.c (revision 24136)
+++ target/linux/ifxmips/files/arch/mips/i
Sorry if this came up before, but i cant find any docu via google and/or
openwrt homepage
I have created some packages in my
~/{buildsystemdirectory}/package/{nameofpackage} directory
and some of them i would have liked before, so i wanted to contribute them
back to the community.
i tried with
Am 22.11.2010 13:24, schrieb Imre Kaloz:
Hi,
On Sun, 21 Nov 2010 12:37:37 +0100, Marcus Osdoba
wrote:
Currently I'm working on improved dockstar support for OpenWrt. The
current toolchain 4.3.3+cs is not that up to date and linaro 4.5 branch
is already included. Unfortunatly, this version doe
This patch adds initial support for arv4510 boards (bewan ibox, wippies
homebox, elisa)
Index: target/linux/ifxmips/files/arch/mips/ifxmips/danube/Kconfig
===
--- target/linux/ifxmips/files/arch/mips/ifxmips/danube/Kconfig (revisión: 2
Hi,
This patch enables pci interrupt setup support for usb controller/minipci
slot of arv7510 boards (wippies homebox, bewan ibox, arv7510)
Index: target/linux/ifxmips/files/arch/mips/pci/pci-ifxmips.c
===
--- target/linux/ifxmips/file
Al 24/11/10 14:18, En/na John Crispin ha escrit:
ok, can you send a patch in that case that makes use of the new pci hook
please so we can apply the patch + a use case
I use the same hook to add support for the atheros ar9223 (using ath9k)
in the arv4518pw.
+static struct ath9k_platform_data
Hi,
"ping?"
gert
- Forwarded message from Gert Doering -
Date: Thu, 11 Nov 2010 14:24:39 +0100
From: Gert Doering
To: openwrt-devel@lists.openwrt.org
Subject: Re: [OpenWrt-Devel] [PATCH] Update for openvpn-devel
the following patch brings openvpn-devel up to "week 45" (most recent)
o
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Yeah, see https://dev.openwrt.org/changeset/24134 .
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAkztPEcACgkQdputYINPTPMScgCfY6YLDt2XCQfdLzKWljacdg2W
bXQAo
hwaddr=$(/sbin/ifconfig $ifname 2>&1 | sed -n 's/^.*HWaddr
\([0-9A-Za-z\-]*\).*/\1/p' | sed -e 's/\-/:/g' | cut -c1-17)
freqs=${freqs:+"$freqs "}$freq
hwmodes=${hwmodes:+"$hwmodes "}$hwmode
diff -urN src/kamikaze/feeds/packages/net/w
r24132 (https://dev.openwrt.org/ticket/8308) introduced the -n flag for
mtd, which is supposed to bypass the erase step. It appears that the
logic used to do this is backwards, and that erasing will actually be
bypassed unless -n is given. Lots and lots of things will break.
(no_erase) needs to ch
ok, can you send a patch in that case that makes use of the new pci hook
please so we can apply the patch + a use case
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
apparnetly i did not get confused ...
could you explain what
--> patch_openwrt_ifxmips_pci_pdevinit.diff
has to do with -->
static struct ath5k_platform_data arv4518_ath5k_platform_data;
static int arv4518_pci_plat_dev_init(struct pci_dev *dev)
{
if ((dev->vendor == PC
Hi John,
> yes, but why does this need a init hook int he pci code ? this should be
> put inside the mach-*.c file imo
Because pcibios_plat_dev_init is a platform specific function, and you can't
override that from machine specific files.
- Gabor
___
o
sorry, i got confused with a different patch that i was sent :)
On 24/11/10 13:31, John Crispin wrote:
> Hi,
>
> yes, but why does this need a init hook int he pci code ? this should be
> put inside the mach-*.c file imo
>
> John
>
>
> On 24/11/10 12:51, ngp ngp wrote:
>> ath5k gets eeprom dat
Hi,
yes, but why does this need a init hook int he pci code ? this should be
put inside the mach-*.c file imo
John
On 24/11/10 12:51, ngp ngp wrote:
> ath5k gets eeprom data from eeprom in card or from platform data of device,
> so if theres no eeprom, this data should be in platform data. Ther
2010.11.24. 12:28 keltezéssel, Roman Yeryomin írta:
> On 24 November 2010 11:56, Gabor Juhos wrote:
>> 2010.11.20. 2:22 keltezéssel, Roman Yeryomin írta:
>>> Why do we need to add DEFAULT_PACKAGES if we have default profile?
>>
>> Why would we have to add those packages to each profile?
>>
>
> ok
2010.11.24. 12:29 keltezéssel, Roman Yeryomin írta:
> On 24 November 2010 12:07, Gabor Juhos wrote:
>> 2010.11.20. 2:35 keltezéssel, Roman Yeryomin írta:
>>> This magic is from original driver. Maybe ramips_esw can be rewritten
>>> to support swconfig but this will do the job for now.
>>> Tested w
ath5k gets eeprom data from eeprom in card or from platform data of device,
so if theres no eeprom, this data should be in platform data. Theres a need
to set this platform data for pci device from platform setup code.
It is similar to whats done in ar71xx.
2010/11/24 John Crispin
> Hi,
>
> i
On 24 November 2010 12:07, Gabor Juhos wrote:
> 2010.11.20. 2:35 keltezéssel, Roman Yeryomin írta:
>> This magic is from original driver. Maybe ramips_esw can be rewritten
>> to support swconfig but this will do the job for now.
>> Tested with Belkin F5D8235 v2 board.
>>
>> Signed-off-by: Roman Ye
On 24 November 2010 11:56, Gabor Juhos wrote:
> 2010.11.20. 2:22 keltezéssel, Roman Yeryomin írta:
>> Why do we need to add DEFAULT_PACKAGES if we have default profile?
>
> Why would we have to add those packages to each profile?
>
ok, then there is no need to list same packages in profiles (this
Hi,
i dont understand why this needs to be in the pci driver
on madwifi we fixed this by patching the driver. the generic pcoi code
should be fully agnostic of the ath5k eep residing in flash.
John
On 24/11/10 11:35, ngp ngp wrote:
> Set platform data to flash stored eeprom for ath5k
>
> stati
Set platform data to flash stored eeprom for ath5k
static struct ath5k_platform_data arv4518_ath5k_platform_data;
static int arv4518_pci_plat_dev_init(struct pci_dev *dev)
{
if ((dev->vendor == PCI_VENDOR_ID_ATHEROS) && (dev->device ==
0xff1b))
dev->dev.platform_data = &a
Hi,
what is the purpose of the hook ?
Thanks,
John
On 24/11/10 01:45, ngp ngp wrote:
> Add hook for platform pci device init. It will permit use of eeprom data
> stored in flash of wireless (ath5k) pci card as platform data.
>
>
>
>
> ___
> openwr
2010.11.20. 2:35 keltezéssel, Roman Yeryomin írta:
> This magic is from original driver. Maybe ramips_esw can be rewritten
> to support swconfig but this will do the job for now.
> Tested with Belkin F5D8235 v2 board.
>
> Signed-off-by: Roman Yeryomin
> --
>
> Index: target/linux/ramips/files/dr
2010.11.20. 2:22 keltezéssel, Roman Yeryomin írta:
> Why do we need to add DEFAULT_PACKAGES if we have default profile?
Why would we have to add those packages to each profile?
- Gabor
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https
Hostapd can allow preauthentication for WPA2-EAP networks when
the interfaces through which preauthentication is allowed are
configured.
Add a new param "rsn_preauth=0/1" to the configuration that enables
or disables preauthentication on the according bridge interface.
Preauthentication for unbri
28 matches
Mail list logo