All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Richardson <mcr@sandelman.ca>
To: linux-wpan@vger.kernel.org
Cc: unstrung-hackers <unstrung-hackers@lists.sandelman.ca>
Subject: testing and building for RPI
Date: Mon, 11 May 2015 15:41:38 -0400	[thread overview]
Message-ID: <19096.1431373298@sandelman.ca> (raw)


I ordered the 802.15.4 module for PI's GPIO pins from:
  http://openlabs.co/OSHW/Raspberry-Pi-802.15.4-radio

got two of them last week, and I dug the RPI out from behind the
TV. (rasbmc.. nice idea, too slow for me)

I haven't yet gotten to caring if I got the right dtbs file,
as discussed here:
   http://forum.openlabs.co/general-oshw-discussion/6lowpan-kernel-on-rpi/

The current linux-wpan-next tree is based on 4.1-rc1, while it
seems that the rpi kernel patches are not merged yet, and rpi-4.0
is based upon 4.0.1.  I tried rebasing the rpi code upon 4.1-rc1
(with linux-wpan-next), but there were two non-trivial merge errors,
and even when I think I got them, some code fails to compile.
I could share that tree with someone if they wanted to help,
as RPI is gonna have to rebase upon 4.1 at some point.

So, I plan to try the opposite, which is to rebase linux-wpan-next
upon 4.0.1.  I imagine that perhaps there is a tree that I've missed
(or isn't tagged) which was before 4.1-rc1 came out... perhaps not.

The question is therefore: have there been any changes in linux-wpan-next
that got accepted into 4.1, and therefore would be missing if I do a
naive cherry-pick?

Will I have to do some dtbs hacking?

--
]               Never tell me the odds!                 | ipv6 mesh networks [
]   Michael Richardson, Sandelman Software Works        | network architect  [
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [


             reply	other threads:[~2015-05-11 19:50 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-11 19:41 Michael Richardson [this message]
2015-05-12  3:52 ` testing and building for RPI Varka Bhadram
2015-05-12  8:28   ` Christoffer Holmstedt
2015-07-21 16:37   ` Michael Richardson
2015-07-30 14:37     ` Stefan Schmidt
2015-07-25 18:27   ` Michael Richardson
2015-07-27  2:14     ` Michael Richardson
2015-07-27  7:39       ` Alexander Aring
2015-07-30 17:39     ` Guido Günther
2015-07-31 13:33       ` Michael Richardson
2016-03-12 21:38         ` Guido Günther

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=19096.1431373298@sandelman.ca \
    --to=mcr@sandelman.ca \
    --cc=linux-wpan@vger.kernel.org \
    --cc=unstrung-hackers@lists.sandelman.ca \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.