Hi,
this look perfect for the uci-defaults file. I did not know about this
section.
Thanks
Il 10/06/2011 14:28, Jo-Philipp Wich ha scritto:
Hi,
without knowing the details here I would argue that a "config domain"
entry in /etc/config/dhcp may be better due to the following reasons:
- I
Hi,
without knowing the details here I would argue that a "config domain"
entry in /etc/config/dhcp may be better due to the following reasons:
- I believe users expect /etc/hosts to be unmanaged, means nothing
writes in there
- The domain entries in /etc/config/dhcp appear in the gui and
Hi,
I would like to have a new entry like:
127.0.0.1 my_name
after a package is installed. the package that i'm installing actually
runs an embedded web server. In this way if I'm attached to the router
using the lan I can point the browser to http://my_name/ instead of
http://10.0.0.1/
R.
On Fri, Jun 10, 2011 at 7:56 AM, Roberto Riggio <
roberto.rig...@create-net.org> wrote:
> Hi,
>
> which is the openwrt way to have a particular package to add
> an entry to /etc/hosts at build or install time? Is it ok to add an
> echo into a uci-defaults file?
>
you could just add it to package
On 10/06/11 13:56, Roberto Riggio wrote:
> Hi,
>
> which is the openwrt way to have a particular package to add
> an entry to /etc/hosts at build or install time? Is it ok to add an
> echo into a uci-defaults file?
>
> R.
>
hi Roberto,
can you give an exymple of where you want to do this ?
Jo
Hi,
which is the openwrt way to have a particular package to add
an entry to /etc/hosts at build or install time? Is it ok to add an
echo into a uci-defaults file?
R.
--
Roberto Riggio, Ph.D.
CREATE-NET
Network& Security Solutions for Pe
On Friday 10 June 2011 11:55:47 Sergiy wrote:
> 10.06.2011 12:44, Florian Fainelli пише:
> > Can you elaborate as to why the kernel cannot use this addresse range? Is
> > this a restriction from the SPI bus not being able to transfer buffers
> > which are in the range 0x8020-0x8022?
>
> Wh
On Fri, Jun 10, 2011 at 11:19 AM, Sergiy wrote:
> This is additional patch for mac80211 package. Due we have flash, that not
> physically mapped, we must get EEPROM data from specific MTD partition.
This doesn't look suitable for upstream (rt2x00 driver) inclusion. A
cleaner way would
be to read
10.06.2011 12:44, Florian Fainelli пише:
Can you elaborate as to why the kernel cannot use this addresse range? Is this
a restriction from the SPI bus not being able to transfer buffers which are in
the range 0x8020-0x8022?
When kernel starting unpatched, it hangs when cleaning init se
Hello,
On Friday 10 June 2011 11:15:49 Sergiy wrote:
> Due buggy nature of this bus, the kernel init section must not use
> addresses at 0x8020...0x8022. Thanks Wive-NG developers for ingo
> about this bug.
>
> This patch must be added into target/linux/ramips/patches-2.6.37 directory
Ca
Hello,
On Friday 10 June 2011 11:13:11 Sergiy wrote:
> Here is SPI-bus implementation for ralink devices.
It is better if you can post the patch inline with your email, makes the
commenting easier.
in ramips_spi_write_read(), there is no check if xfer->len is not bigger than
the controller FIF
This is additional patch for mac80211 package. Due we have flash, that
not physically mapped, we must get EEPROM data from specific MTD partition.
--- a/drivers/net/wireless/rt2x00/rt2800pci.c
+++ b/drivers/net/wireless/rt2x00/rt2800pci.c
@@ -40,6 +40,11 @@
#include
#include
+#if defined(CON
Our device seems don't have any additional leds, so we don't use gpio-leds.
Index: target/linux/ramips/files/arch/mips/ralink/rt305x/Kconfig
===
--- target/linux/ramips/files/arch/mips/ralink/rt305x/Kconfig (revision 26927)
+++ target
Due buggy nature of this bus, the kernel init section must not use
addresses at 0x8020...0x8022. Thanks Wive-NG developers for ingo
about this bug.
This patch must be added into target/linux/ramips/patches-2.6.37 directory
+++ a/arch/mips/kernel/vmlinux.lds.S
+++ b/arch/mips/kernel/vmli
Here is SPI-bus implementation for ralink devices.
Index: target/linux/ramips/files/arch/mips/ralink/rt305x/devices.c
===
--- target/linux/ramips/files/arch/mips/ralink/rt305x/devices.c (revision 26927)
+++ target/linux/ramips/files/a
15 matches
Mail list logo
