Then it'd make total sense to stuff in whatever fits there .. thanks for
the enlightenment, ede

On 10.05.2010 23:38, Matthias Buecher / Germany wrote:
> The "linux" partition spans over the kernel and the complete rootfs for
> flashing.
> The maximum kernel size is 0x000bc000 (begin of "rootfs") minus
> 0x00040000 (begin of "linux") equals 0x0007c000 (496KB).
> 
> Maddes
> 
> On 10.05.2010 23:34, edgar.sol...@web.de wrote:
>> are these sizes fixed or calculated according the space requirement?
>> Looks like the linux size is fixed, what is the maximum size for a
>> kernel on wrt54g?
>>
>> .. ede
>>
>> On 10.05.2010 23:28, Matthias Buecher / Germany wrote:
>>> Kernel and rootfs are in two different mtd partitions on the WRT54G:
>>>
>>> # dmesg
>>> ...
>>> Creating 5 MTD partitions on "Physically mapped flash":
>>> 0x00000000-0x00040000 : "cfe"
>>> 0x00040000-0x003f0000 : "linux"
>>> 0x000bc000-0x00210000 : "rootfs"
>>> mtd: partition "rootfs" doesn't start on an erase block boundary --
>>> force read-only
>>> 0x003f0000-0x00400000 : "nvram"
>>> 0x00210000-0x003f0000 : "rootfs_data"
>>> ...
>>>
>>> So it is moved from "rootfs" to "linux" in this case.
>>>
>>> Maddes
>>>
>>> On 10.05.2010 22:53, edgar.sol...@web.de wrote:
>>>> but wouldn't the increase in the kernel image actually equal the
>>>> decrease in the squash image and therefore the size of the rootfs_data
>>>> stay the same? Both are lzma compressed.
>>>>
>>>> ..ede
>>>>
>>>>
>>>> On 10.05.2010 19:16, Matthias Buecher / Germany wrote:
>>>>> It may not downsize the packages themselves, but moving kernel mods from
>>>>> rootfs to the kernel image will reduce the rootfs size. Leaving more
>>>>> space for JFFS2 rootfs_data.
>>>>>
>>>>> Having a "K" setting for kernel options would be great.
>>>>> Will try to have a look at it during the next weeks.
>>>>>
>>>>> Thanks for all your help
>>>>> Maddes
>>>>>
>>>>> On 10.05.2010 17:20, edgar.sol...@web.de wrote:
>>>>>> there is partly in
>>>>>> https://dev.openwrt.org/browser/trunk/include/kernel-defaults.mk
>>>>>> line 101
>>>>>>
>>>>>> you can actually add
>>>>>> CONFIG_KERNEL_*
>>>>>> entries to your .config and they are copied over as CONFIG_* to the
>>>>>> kernel config. All that's missing is a menuconfig interface for that.
>>>>>>
>>>>>> But at least for routers using lzma squashfs for the initial image this
>>>>>> will probably not downsize anything.
>>>>>>
>>>>>> .. ede
>>>>>>
>>>>>>
>>>>>> On 10.05.2010 16:19, Stefan Monnier wrote:
>>>>>>>> In 'make menuconfig' I included them with 'Y' instead of 'M'.
>>>>>>>> According to my (newbie) knowledge that adds them to the kernel image.
>>>>>>>> Can somebody please confirm my understanding? Or at least prove me
>>>>>>>> wrong? :D
>>>>>>> Damn! I thought you had found a clever way to get them compiled into
>>>>>>> the kernel.
>>>>>>> I still hope some day someone will write the extra code needed so that
>>>>>>> "make menuconfig" can be told to build some modules right into
>>>>>>> the kernel.
>>>>>>>
>>>>>>>
>>>>>>>          Stefan
>>>>>>>
>>>>> _______________________________________________
>>>>> openwrt-devel mailing list
>>>>> openwrt-devel@lists.openwrt.org
>>>>> https://lists.openwrt.org/mailman/listinfo/openwrt-devel
>>>> _______________________________________________
>>>> openwrt-devel mailing list
>>>> openwrt-devel@lists.openwrt.org
>>>> https://lists.openwrt.org/mailman/listinfo/openwrt-devel
>>> _______________________________________________
>>> openwrt-devel mailing list
>>> openwrt-devel@lists.openwrt.org
>>> https://lists.openwrt.org/mailman/listinfo/openwrt-devel
>>
>> _______________________________________________
>> openwrt-devel mailing list
>> openwrt-devel@lists.openwrt.org
>> https://lists.openwrt.org/mailman/listinfo/openwrt-devel
> _______________________________________________
> openwrt-devel mailing list
> openwrt-devel@lists.openwrt.org
> https://lists.openwrt.org/mailman/listinfo/openwrt-devel

_______________________________________________
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Reply via email to