Yes. spimodule should be pushed up to meta-openembedded as
python-spimodule. I found the original source thesis site last night and
will work on a patch for meta-oe.

As for eeprom--- we probably need to write a script that can be run on BBB.
I was rather blindly writing that recipe without realizing it needed to be
run on the target.

Once spimodule is pushed upstream, we won't need redeem-libs anymore.

Also, pasm/libprussdrv need to be pushed upstream to meta-beagleboard.

Also, tty0tty should be pushed upstream to meta-openembedded.


On Sun, Nov 24, 2013 at 9:13 AM, eliasbakken <notifications@github.com>wrote:

> In recipes-bsp/redeem/redeem_0.7.2.bb:
>
> > +FILES_${PN} += " \
> > +            ${D}/opt \
> > +            ${D}/opt/Replicape \
> > +            ${D}/opt/Replicape/software/*.py \
> > +            ${D}/opt/Replicape/software/*.so \
> > +            ${D}/opt/Replicape/software/config \
> > +            ${D}/opt/Replicape/software/config/Thing.cfg \
> > +"
> > +inherit distutils
> > +
> > +export BUILD_SYS
> > +export HOST_SYS
> > +export STAGING_INCDIR
> > +export STAGING_LIBDIR
> > +
> > +BBCLASSEXTEND = "native"
>
> Tim, about the EEPROM. Is it trying to flash the eeprom on the host?
> do_install () { install -d ${D}/sys/bus/i2c/drivers/at24/1-0054 cp
> ${S}/Replicape.eeprom ${S}/eeprom install -m 0644 ${S}/eeprom
> ${D}/sys/bus/i2c/drivers/at24/1-0054/ } This needs to be done on the
> BeagleBone itself, since it is actually flashing a physical EEPROM chip. Do
> you have any idea how this can be done?
> … <#1428b1a804d33311_>
> On Sun, Nov 24, 2013 at 5:43 PM, Elias Bakken <elias.bakken@gmail.com>wrote:
> > Ah.. I was working on the wrong file... *Facepalm* > > > On Sun, Nov 24,
> 2013 at 5:35 PM, Elias Bakken <elias.bakken@gmail.com>wrote: > >> Tim,
> thanks for the update! I have fetched and merged the changes. I'm >> now
> looking at cleaning up a few things, moving the spi module and changing >>
> lisence (GPLv2, it's not my work). Also, It is a stand alone python module,
> >> so it should be pushed upstream asap. I also want to change the name of
> the >> Redeem-software and handle the dependencies right so that users only
> have >> to write "opkg install redeem" and dependencies will be handled. >>
> >> What I am having trouble with is updating a repository from oe/bitbake.
> I >> have changed the SRCREV variable in a recipe, but I cannot get Bitbake
> to >> pull new changes. How do I do that? >> >> >> On Sun, Nov 24, 2013 at
> 6:45 AM, moto-timo <notifications@github.com>wrote: > >> In
> recipes-bsp/redeem/redeem_0.7.2.bb: >> >> > +FILES_${PN} += " \ >> > +
> ${D}/opt \ >> > + ${D}/opt/Replicape \ >> > +
> ${D}/opt/Replicape/software/*.py \ >> > + ${D}/opt/Replicape/software/*.so
> \ >> > + ${D}/opt/Replicape/software/config \ >> > +
> ${D}/opt/Replicape/software/ >> config/Thing.cfg \ >> > +" >> > +inherit
> distutils >> > + >> > +export BUILD_SYS >> > +export HOST_SYS >> > +export
> STAGING_INCDIR >> > +export STAGING_LIBDIR >> > + >> > +BBCLASSEXTEND =
> "native" >> >> Only applies if you want a native version that runs on the
> host >> >> — >> Reply to this email directly or view it on GitHub<
> https://github.com/moto-timo/meta-replicape/pull/2/files#r7878061> >> .
> >> > > > > -- > Vennlig hilsen Elias > -- Vennlig hilsen Elias
>  -- Vennlig hilsen Elias
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/moto-timo/meta-replicape/pull/2/files#r7879288>
> .
>