ORBIT-USER: ORBIT Node kernel version

[Rodney Berriman]

Hello Luis,

 we are also using a custom kernel for our wireless mesh testbed, e.g. 
to fix the bug in via-rhine.c which affects our VIA mini-ITX cards.

 Could you please confirm or not that the wireless development tree will 
work with libmac?

 If not, is there a patch available, or a set of instructions to patch 
the madwifi driver for libmac?

many thanks,
Rodney
NICTA



Luis R. Rodriguez wrote:
> At the moment orbit is designed so you can only use the images we have
> or you save; you use them the usual imageNodes process. If you want
> the latest wireless kernel development tree yourself just:
>
> cg-clone 
> git://git.kernel.org/pub/scm/linux/kernel/git/linville/wireless-dev.git
>
>  Luis
>
> On 10/3/06, Arinto Murdopo <arinto at gmail.com> wrote:
>> Okie, where can I download the baseline image?
>>
>> Thank you
>>
>> arinto
>>
>>
>> On 10/4/06, Luis R. Rodriguez < mcgrof at gmail.com > wrote:
>> > Arinto,
>> >
>> > For anything that has to do with linux wireless development you should
>> > be using our wireless development images or your own. Linux is under
>> > heavy wireless development right now so bleeding edge is the way to go
>> > as otherwise you'd miss out on patches for fixes, additions and API
>> > changes. This specially holds true if you wish to eventually submit
>> > your protocol upstream. Patches for additions of new protocols should
>> > always be based on the latest and greatest.
>> >
>> > The list of supported images is always available at:
>> >
>> > http://orbit-lab.org/wiki/Documentation/SupportedImages
>> >
>> > If you use these you'll also get kernel debugging as a perk ;)
>> >
>> >   Luis
>> >
>> > On 9/26/06, Sachin Ganu <sachin at winlab.rutgers.edu> wrote:
>> > > We have 2.6.12 in our baseline image
>> > >
>> > > On 9/25/06, Arinto Murdopo < arinto at gmail.com> wrote:
>> > > > How about for the kernel itself? I think I need to develop my 
>> protocol
>> in
>> > > > the same kernel version as ORBIT node.. I'm afraid my protocol 
>> would
>> not be
>> > > > able to run smoothly if developing kernel is different from ORBIT
>> node's
>> > > > kernel version.
>> > > >
>> > > > Thank you for your attention
>> > > >
>> > > > arinto
>> > > >
>> > > >
>> > > > On 9/26/06, Sachin Ganu < sachin at winlab.rutgers.edu > wrote:
>> > > > > Hi Arinto,
>> > > > >
>> > > > > As ORBIT users, we would ideally like a debian package that 
>> can be
>> > > > > simply apt-get installed. However, we are currently not 
>> averse to
>> you
>> > > > > having your own hard disk images given the tradeoff between 
>> the time
>> > > > > it takes for the debianization and the convenience of using 
>> custom
>> > > > > images.
>> > > > >
>> > > > > One example you can look at is the OTG code's Makefile .. its 
>> fairly
>> > > > > easy to adapt that to create your own binary Debian package 
>> for your
>> > > > > app.
>> > > > >
>> > > > > On 9/24/06, Arinto Murdopo < arinto at gmail.com > wrote:
>> > > > > > Dear All
>> > > > > >
>> > > > > > If I want to develop some protocol and in the end I'll 
>> upload it
>> to
>> > > > ORBIT,
>> > > > > > which kernel version I should use? The latest stable kernel in
>> > > > kernel.org is
>> > > > > > version 2.6.18. Is that ok if using this kernel?
>> > > > > >
>> > > > > > Which one is easier and more reliable, imaging the whole OS 
>> image
>> to the
>> > > > > > node so the protocol will be installed with the OS where it is
>> developed
>> > > > OR
>> > > > > > make the protocol as an application under Debian linux so 
>> we can
>> install
>> > > > in
>> > > > > > Debian node using apt feature of Debian? Anyone has experience
>> this
>> > > > before?
>> > > > > > Maybe you can share your experience and suggestion
>> > > > > >
>> > > > > > Thank you for your help and attention
>> > > > > >
>> > > > > > arinto
>> > > > > >
>> > > > > >
>> > > > > >
>> > > > >
>> > > >
>> > > >
>> > >
>> >
>>
>>



--------------------------------------------------------------------------
This email and any attachments may be confidential. They may contain legally
privileged information or copyright material. You should not read, copy,
use or disclose them without authorisation. If you are not an intended
recipient, please contact us at once by return email and then delete both
messages. We do not accept liability in connection with computer virus,
data corruption, delay, interruption, unauthorised access or unauthorised
amendment. This notice should not be removed.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://orbit-lab.org/pipermail/orbit-user/attachments/20061010/b2f6ea89/attachment.htm