20 May
2013
20 May
'13
6:18 p.m.
Hi Pau and SAn,
during the brainstorming sessions that gave birth to libre-mesh we
talked about integrating qmpfw and the firmware Chef.
Pau and SAn are the guys behind the development of these tools, maybe it
would be interesting to start coordinating how this can be actually
implemented?
Cheers,
Nico.
20 May
20 May
7:09 p.m.
Ok for me, we can discuss the details using the mailing list.
The "lime-build" source code in github should work to generate some
testing images. I copy&paste what I posted in other private mail about that.
If you clone the repository lime-build and type "make T=tl-703n J=2",
it should compile the system with the lime-system enabled and the
dependences.
For the moment only the targets tl-703n and tl-wdr4300 are supported,
but it is just a mather of adding the config files in the
configs/directory
To create them execute
- make T=NEW_TARGET menuconfig
- find the resulting config file in build/configs/NEW_TARGET
- diffconfig it with build/ar71xx/scripts/
diffconfig (yes, it should
be added to the Makefile to do it automatically, please volunteeers!!)
- save it to configs/NEW_TARGET
Following this approach we can have kind of useful diferent profiles
for each target. So, some software can fit in devices such as wdr4300
and not in 703n.
On 20/05/13 20:18, NicoEchániz wrote:
Hi Pau and SAn,
during the brainstorming sessions that gave birth to libre-mesh we
talked about integrating qmpfw and the firmware Chef.
Pau and SAn are the guys behind the development of these tools, maybe it
would be interesting to start coordinating how this can be actually
implemented?
Cheers,
Nico.
_______________________________________________
Dev mailing list
Dev(a)lists.libre-mesh.org
https://lists.libre-mesh.org/mailman/listinfo/dev
--
./p4u
21 May
21 May
3:41 p.m.
Hi!
On Mon, May 20, 2013 at 4:09 PM, Pau <pau(a)dabax.net> wrote:
Ok for me, we can discuss the details using the
mailing list.
The "lime-build" source code in github should work to generate some testing
images. I copy&paste what I posted in other private mail about that.
If you clone the repository lime-build and type "make T=tl-703n J=2",
it should compile the system with the lime-system enabled and the
dependences.
For the moment only the targets tl-703n and tl-wdr4300 are supported,
but it is just a mather of adding the config files in the
configs/directory
To create them execute
- make T=NEW_TARGET menuconfig
- find the resulting config file in build/configs/NEW_TARGET
- diffconfig it with build/ar71xx/scripts/
diffconfig (yes, it should
be added to the Makefile to do it automatically, please volunteeers!!)
- save it to configs/NEW_TARGET
Following this approach we can have kind of useful diferent profiles
for each target. So, some software can fit in devices such as wdr4300
and not in 703n.
Thanks for the input Pau. I looked the code and talked yesterday with
guido. We will be doing some tests so we can understand better qmpfw
and how to use it from the chef.
I dont see crearly if using qmpfw as is directly from the web
interface is the way to go, because, like ImageBuilder, there are
multiple points of failure and it seems that a developer eye in the
process is needed. What do you think?
cheers!,
SAn
3:52 p.m.
It is hard to say, I don't know how Chef is working internally.
The idea is to have the lime-build already prepared (with all the
sources compiles) and then only execute it from the web to generate the
desired image with some small customizations.
However qmpfw (lime-build) was not developed for this scope, it is a
tool for developers to easy compile/modify the sources of the firmware.
Maybe then it is better to use ImageBuilder, I don't know.
Using lime-build, the shell call to compile an image (from the web
interface) would be the next:
make T=tl-wdr4300 P=altermesh build
Where T is the target and P is the profile. The profile is mainly a set
of configuration files (for instance /etc/config/lime-defaults) which
are used by the community (not yet implemented but easy).
To put custom files (for instance a custom /etc/shadow), they should be
written to the files/ directory placed in the root directory of lime-build.
This is all I can say for the moment :-P
On 21/05/13 17:41, SAn wrote:
Hi!
On Mon, May 20, 2013 at 4:09 PM, Pau <pau(a)dabax.net> wrote:
--
./p4u
Ok for me, we can discuss the details using the
mailing list.
The "lime-build" source code in github should work to generate some testing
images. I copy&paste what I posted in other private mail about that.
If you clone the repository lime-build and type "make T=tl-703n J=2",
it should compile the system with the lime-system enabled and the
dependences.
For the moment only the targets tl-703n and tl-wdr4300 are supported,
but it is just a mather of adding the config files in the
configs/directory
To create them execute
- make T=NEW_TARGET menuconfig
- find the resulting config file in build/configs/NEW_TARGET
- diffconfig it with build/ar71xx/scripts/
diffconfig (yes, it should
be added to the Makefile to do it automatically, please volunteeers!!)
- save it to configs/NEW_TARGET
Following this approach we can have kind of useful diferent profiles
for each target. So, some software can fit in devices such as wdr4300
and not in 703n.
Thanks for the input Pau. I looked the code and talked yesterday
with
guido. We will be doing some tests so we can understand better qmpfw
and how to use it from the chef.
I dont see crearly if using qmpfw as is directly from the web
interface is the way to go, because, like ImageBuilder, there are
multiple points of failure and it seems that a developer eye in the
process is needed. What do you think?
cheers!,
SAn
_______________________________________________
Dev mailing list
Dev(a)lists.libre-mesh.org
https://lists.libre-mesh.org/mailman/listinfo/dev
4545
days inactive
4546
days old
3 comments
3 participants
participants (3)
-
NicoEchániz -
Pau -
SAn