Request for the information on PandaBoard Linux BSP
Suresh Acharya
Work/Company/Job: I work for Sasken Communication as Software
Architect
What’s up with me and Pandaboard:
- About 9 years worked on different OMAP flavours. 18 years writing
hardware centric software across multiple ARM platforms
- Active TI E2E member
- Participating in PandaBoard's early adopter program. I don't have
any Pandaboard yet.
- I am not sure at what state the Pandaboard BSP are now on Linux.
Want to definitely explore more. Any information regarding this is
very helpful
- I want to provide MeeGo support on Pandaboards. I'll continue to
work with the community to contribute towards supporting MeeGo on
Pandaboard
IRC Nick: acharya on irc.freenode.net
Dr. H. Nikolaus Schaller
> - I am not sure at what state the Pandaboard BSP are now on Linux.
> Want to definitely explore more. Any information regarding this is
> very helpful
The source repository appears to be here
http://gitorious.org/PandaBoard
I have not yet looked into details since I don't have a Pandaboard yet,
except that the Makefile starts with:
VERSION = 2
PATCHLEVEL = 6
SUBLEVEL = 36
EXTRAVERSION = -rc2
Nikolaus
Vincent Stehlé
> The source repository appears to be here
> http://gitorious.org/PandaBoard
Hi,
You may also want to refer to the Ubuntu (maverick) kernel, which has
good (and tested) support for the pandaboard:
http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-maverick.git;a=shortlog;h=refs/heads/ti-omap4
Best regards,
--
Vincent Stehl�
Systems Engineer - TI France
Nishanth Menon
On Oct 14, 12:05 am, Suresh Acharya <asachar...@gmail.com> wrote:
> - I want to provide MeeGo support on Pandaboards. I'll continue to
> work with the community to contribute towards supporting MeeGo on
> Pandaboard
MeeGo has a requirement that ALL patches that are submitted should be
either already in kernel.org OR on the way to being merged in to
kernel.org (through one of the maintainers). More:
http://wiki.meego.com/MeeGo_kernel_documentation_for_contributors
Current status of MeeGo and Pandaboard -
Working on kernel-dev package - 2.6.36-rc4
Yogesh and I (both of us from TI) have been working on cherrypicking
patches for 2.6.34-rc4 with the intent of getting at least a shell
prompt up and running. We have some level working. unfortunately we
have'nt been able to get mmc to mount up yet (as of yesterday evening
CST).
I have already created rpm packages for u-boot and x-loader in my
build.meego.com repos - unfortunately i need to deal with gcc 4.5
related issues as well there.. James Mills & Jaime Garcia (both from
TI) have been working on getting a kickstart file up and running, but
ran into limitations of libgparted with mic2 for creating bootable
partitions. James is looking to provide mic2 support with sfdisk over
the next few days/weeks hopefully.
in parallel suren has been working to get support for gstreamer
package and omap4.
Things to do: for collaboration, I am planning to host up a git tree
atleast somewhere on gitorious/github so that we can all work
together. I will release the info on meego-kernel ML and drop a note
on pandaboard ML as well..
Channels of discussion:
omap kernel: freenode.net: #linux-omap on freenode.net, mailing list:
http://vger.kernel.org/vger-lists.html#linux-omap (if OMAP kernel
patches are being provided)
meego specific kernel discussion: http://lists.meego.com/listinfo/meego-kernel
All meego arm discussions on #meego-arm on freenode.net
Pandaboard related discussions: #pandaboard and this mailing list
to be in sync, the irc nicks of folks involved in someway so far are:
#meego-arm: Stskeeps - Cartsen Munk - N900 Maintainer for Meego and
excellent guidance for all things meego :)
Other Nicks:
awayfar - James
yogeshd - Yogesh
suren - Suren
felidiso - Jamie
NishanthMenon - your's truely
you'd find the above folks lurking around in #linux-omap, #pandaboard,
#meego-arm and #meego.
Steps ahead:
Feel free to contribute in any area of your interest - we have scope
for lot of help :) - we prefer to have public discussions in public
MLs as much as possible. all solutions are prefered to be mainlined, I
prefer not to carry patches for ever :)
Regards,
Nishanth Menon
Nishanth Menon
On Oct 14, 7:42 am, Nishanth Menon <menon.nisha...@gmail.com> wrote:
> Things to do: for collaboration, I am planning to host up a git tree
> atleast somewhere on gitorious/github so that we can all work
> together. I will release the info on meego-kernel ML and drop a note
> on pandaboard ML as well..
http://lists.meego.com/pipermail/meego-kernel/2010-October/000577.html
I have already asked the meego kernel maintainers on what they'd like
to do with
kernel-dev branch.. lets see. meanwhile the next tasks to do:
display (yaay - for omapfb) and ehci! all participation welcome :)
Regards,
Nishanth Menon
PS: full meego thread here:
http://lists.meego.com/pipermail/meego-kernel/2010-October/thread.html#575
Suresh Acharya
Thanks for the detailed email. My progress is slow and hence you could
see delay in reply as I am working on this in my free time.
Few concerns I have are the following.
1. As I don't have a board and ordering now, my contribution in this
forum will be delayed.
2. Do we have some deadline, where in we should deliver what we agreed
upon?
Thanks ... Suresh
Nishanth Menon
> Nishanth,
>
> Thanks for the detailed email. My progress is slow and hence you could
> see delay in reply as I am working on this in my free time.
>
> Few concerns I have are the following.
>
> 1. As I don't have a board and ordering now, my contribution in this
> forum will be delayed.
> 2. Do we have some deadline, where in we should deliver what we agreed
> upon?
There are no defined deadlines per-se - community contributions are
welcome, any time of your choice and in any area of your choice.
That said, we are targeting to do a demo in MeeGo conference in
Dublin[1] and that is on Nov 15 :).. yaay.. pretty short timeframe :D.
But, dont feel constrained to try anything out like kick start files
etc before hand.. it is entirely upto you :)
Thanks once again for your interest in participating - if you'd like
to contribute on anything just drop an email on meego-dev ML, I am
sure we have folks out there who can suggest areas that MeeGo
community might like a bit of a hand :) - you could even join in the
MeeGo kernel/dev/community mailing list, browse through the emails
when ever you choose and even help us by providing your views or
comments on some of the discussion topics.
Hoping to hear more from you on MeeGo family.. :)
Regards,
Nishanth Menon