I'm wondering why the 8.09 RC1 announcement was not made here. It was
made on the "forums" at
http://forum.openwrt.org/viewtopic.php?pid=75990. Do we really have to
subject ourselves to the far inferior interface of silly "forums" in
order to be up to date on this stuff?
Mailing lists are where
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Florian Fainelli schrieb:
> Hallo Alex,
>
> Nicht alle OpenWrt developers sprechen Deutsch ;)
>
> (my approximate translation below)
>
thanks for translating, as i am a lazy fart, i would have delayed it
until too late.
one reason for at least CCi
Hi Brian,
This was introduced with the FireWire modules recently added, enabling
FireWire support in the kernel when they're selected.
It should be fixed in [13169].
Cheers,
--
Nico
Brian J. Murrell wrote:
> Using Kamikaze r13161 every time I run a make I get prompted for the
> following kern
Florian Fainelli wrote:
> What do you think about getting a meeting (with Palinka and Absinthe) like
> last year so that we can expose OpenWrt plans for the future and answer
> questions ?
hello, from c-base
the best day for a meeting in the c-base mainhall like last year would
be Mo 29.Dez.2
Hallo Alex,
Nicht alle OpenWrt developers sprechen Deutsch ;)
(my approximate translation below)
Le Monday 10 November 2008 18:27:35 Alexander Morlang, vous avez écrit :
> Hi,
> das übliche Freifunk/wireless/openwrt/etc. konglomerat wird sich auch
> auf dem kommenden chaos communication congress
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
das übliche Freifunk/wireless/openwrt/etc. konglomerat wird sich auch
auf dem kommenden chaos communication congress treffen.
Die Raumplanung ist bisher noch nicht abgeschlossen, sobald dies
geschehn ist werden wir exakt wissen, wo wir uns diesmal
--- On Mon, 10/11/08, Harald Schiöberg <[EMAIL PROTECTED]> wrote:
> From: Harald Schiöberg <[EMAIL PROTECTED]>
> Subject: Re: [OpenWrt-Devel] repeated kernel config questions
> To: "OpenWrt Development List"
> Date: Monday, 10 November, 2008, 2:52 PM
> -BEGIN PGP SIGNED MESSAGE-
> Hash: S
actually in my patch
http://lists.openwrt.org/pipermail/openwrt-devel/2008-October/003249.html
I offered a way to modify kernel config from a board profile-specific file.
Same thing can be easily done for user files in ./files
- Original Message
> From: Stanislav Sinyagin <[EMAIL PROT
On Mon, 2008-11-10 at 06:21 -0800, Stanislav Sinyagin wrote:
> The makefiles override the kernel config each time you do "make menuconfig".
> It's not a bug, it's so by design :)
So the question is, why don't I get asked about every other kernel
config option? Whatever prevents that from happenin
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Stanislav Sinyagin wrote:
> this is what I remember from the time I tried to adapt this to my needs.
> Remembering the values would not be too much of a critical thing, if
> the kernel parameters would be settable from the user files. There's
> a pla
Quoting bifferos <[EMAIL PROTECTED]>:
> I think he means ones like this:
> https://dev.openwrt.org/browser/trunk/target/linux/generic-2.6/config-2.6.27
>
> I'd really love this to be fixed, because it makes building custom
> kernels a nuisance. Presumably it's done this way because it makes
> thi
this is what I remember from the time I tried to adapt this to my needs.
Remembering the values would not be too much of a critical thing, if
the kernel parameters would be settable from the user files. There's
a place for that in ./files, but this behavior is not implemented.
- Original M
--- On Mon, 10/11/08, Brian J. Murrell <[EMAIL PROTECTED]> wrote:
> From: Brian J. Murrell <[EMAIL PROTECTED]>
> Subject: Re: [OpenWrt-Devel] repeated kernel config questions
> To: "OpenWrt Development List"
> Date: Monday, 10 November, 2008, 1:53 PM
> On Mon, 2008-11-10 at 08:44 -0500, Robert P.
Quoting Stanislav Sinyagin <[EMAIL PROTECTED]>:
> The makefiles override the kernel config each time you do "make menuconfig".
> It's not a bug, it's so by design :)
really? i don't have the build structure in front of me,
but the standard kernel config recipe is that, if you have
no .config
The makefiles override the kernel config each time you do "make menuconfig".
It's not a bug, it's so by design :)
- Original Message
> From: Brian J. Murrell <[EMAIL PROTECTED]>
> To: OpenWrt Development List
> Sent: Monday, November 10, 2008 2:53:35 PM
> Subject: Re: [OpenWrt-Devel] r
On Mon, 2008-11-10 at 08:44 -0500, Robert P. J. Day wrote:
>typically, you will be perpetually asked about "NEW" kernel
> options if the default config file has no mention of them.
Which default config file is this and why are my answers not being
remembered from one make world to another as t
Quoting "Brian J. Murrell" <[EMAIL PROTECTED]>:
> On Mon, 2008-11-10 at 14:03 +0100, Gregers Petersen wrote:
>>
>> Did you try 'make clean' and then a new 'menuconfig' ?
>
> I did make clean before I did make oldconfig. Why should I need to make
> menuconfig? I don't want to use the stupid menu
On Mon, 2008-11-10 at 14:03 +0100, Gregers Petersen wrote:
>
> Did you try 'make clean' and then a new 'menuconfig' ?
I did make clean before I did make oldconfig. Why should I need to make
menuconfig? I don't want to use the stupid menu interface. make
oldconfig should achieve the same thing,
Hi,
I'm trying to figure out how to add start scripts directly in the
buildsystem. How is that done?
NOTE: I know how to create the links "by hand" with /etc/init.d/myscript
enable but I like the build system to create them directly in the image.
Any pointers?
// Jimmy
__
Brian J. Murrell wrote:
> Using Kamikaze r13161 every time I run a make I get prompted for the
> following kernel options:
>
> Excessive debugging output (IEEE1394_VERBOSEDEBUG) [N/y/?] (NEW)
> Texas Instruments PCILynx support (IEEE1394_PCILYNX) [N/m/?] (NEW)
> Enable replacement for ph
Using Kamikaze r13161 every time I run a make I get prompted for the
following kernel options:
Excessive debugging output (IEEE1394_VERBOSEDEBUG) [N/y/?] (NEW)
Texas Instruments PCILynx support (IEEE1394_PCILYNX) [N/m/?] (NEW)
Enable replacement for physical DMA in SBP2 (IEEE1394_SBP2_PH
21 matches
Mail list logo
