Marvell Kirkwood - anyone?

Balanga Bar balanga.bar at gmail.com
Sat Apr 27 08:44:44 UTC 2019


Didn't you need to include '-DWITH_FDT' ?

As for 'unable to build'... I would run make in a directory under
/usr/ports and there would be no response. The system would just hang.

I have now managed to install 11.1 which seems fairly stable and have built
a few pkgs, although building them takes several hours. It would be much
better if I was able to build them under amd64, but haven't found a way of
doing that yet

On Thu, Apr 25, 2019 at 3:01 PM Ronald Klop <ronald-lists at klop.ws> wrote:

> On Thu, 25 Apr 2019 11:15:05 +0200, Balanga Bar <balanga.bar at gmail.com>
> wrote:
>
> It's nice to know that someone has 11.2 working on armv5. Could you let me
> know how you built it?
>
>
>
> I cross-compiled on amd64.
> cd /usr/src (containing the 11.2 sources of course)
> export TARGET_ARCH=arm
> export KERNCONF=SHEEVAPLUG
> export DESTDIR=/mnt/usbdisk (here the usb stick is mounted)
> make buildworld
> make buildkernel
> cp /usr/obj/arm.arm/usr/src/sys/SHEEVAPLUG/kernel.bin $DESTDIR/boot/msdos/
> make installworld
> make distribution
>
> From the top of my head, so I might have missed something.
>
>
>
> I installed portsnap under 11.0 but was unable to build anything - will
> try again with 11.2 to see if I can iron out the problems I've had as I now
> know someone has it working.
>
>
> "Unable to build" is not very specific. It helps if you copy paste the
> actual error message.
>
> Ronald.
>
>
>
> On Wed, Apr 24, 2019 at 10:34 AM Ronald Klop <ronald-lists at klop.ws> wrote:
>
>> Dear Balanga,
>>
>> I run 11.2 on my Sheevaplug (armv5 also).
>>
>> uname -a
>> FreeBSD sheeva2.klop.ws 11.2-RELEASE-p4 FreeBSD 11.2-RELEASE-p4 #4
>> r339336M: Sat Oct 13 23:31:51 CEST 2018     builder at rpi3:/data/src/obj-11.2/arm.arm/data/src/11.2/sys/SHEEVAPLUG
>> arm
>>
>> It has a ports checkout using portsnap. And that works pretty well.
>> Just do:
>> portsnap auto
>> cd /usr/ports/shells/bash (or whatever port you wish to install)
>> make install
>> make clean
>>
>> I think that is the most simple approach for you to go forward.
>>
>> Regards,
>> Ronald.
>>
>> PS: Sorry for top-posting, my current mail client does not help in this
>> very well.
>>
>>
>> *Van:* Balanga Bar <balanga.bar at gmail.com>
>> *Datum:* dinsdag, 23 april 2019 20:08
>> *Aan:* Mark Linimon <linimon at lonesome.com>
>> *CC:* freebsd-arm at freebsd.org, Ian Lepore <ian at freebsd.org>
>> *Onderwerp:* Re: Marvell Kirkwood - anyone?
>>
>> Actually I have managed to build FreeBSD 11.0-RELEASE on ARM and it has
>> not
>> exhibited any problems on my GoFlexHome apart from being unable install
>> pkgs. That is the current focus at the moment.
>>
>> On Tue, Apr 23, 2019 at 5:57 PM Mark Linimon <linimon at lonesome.com>
>> wrote:
>>
>> > On Tue, Apr 23, 2019 at 03:19:15PM +0100, Balanga Bar wrote:
>> > > Is it possible to get a version of portsnap from that point?
>> >
>> > I don't know enough to answer that question.  I think it would be fair
>> > to assume "no".
>> >
>> > IIUC you seem to be looking for an _easy_ way to get Kirkwood back up
>> > and working.  I'm going to be honest and say there isn't one.
>> >
>> > Here are the approaches I think you can take:
>> >
>> >  - stay on 8.x; bring individual port updates to it from ports-head and
>> >    build your own ports.  Difficulty: hard.
>> >
>> >  - figure out what src changes after 8.x regressed Kirkwood; check
>> >    out src 12-STABLE, build your own src, and use FreeBSD.org packages.
>> >    Difficulty: expert.
>> >
>> >  - stay on 8.x; attempt to bring a modern ports tree to it and build
>> >    your own ports.  Difficulty: challenging.
>> >
>> > The difficulty level of the first approach depends on which ports you
>> > are going to try to use.  shells/bash?  Probably not too hard.  Anything
>> > GUI-related?  Very hard.
>> >
>> > None of these approaches are achievable within hours; they will take
>> > days, or, in the case of the third approach, weeks.
>> >
>> > fwiw, the second approach is the only one where your fixes could be
>> > merged back into FreeBSD.  If I were personally determined to run
>> > Kirkwoord, that's the approach I would take.  (I gave my GuruPlug
>> > away some time ago.)
>> >
>> > I'm sorry that I can't be more encouraging.
>> >
>> > mcl
>> >
>> _______________________________________________
>> freebsd-arm at freebsd.org mailing list
>> https://lists.freebsd.org/mailman/listinfo/freebsd-arm
>> To unsubscribe, send any mail to "freebsd-arm-unsubscribe at freebsd.org"
>> ------------------------------
>>
>>
>
>
>


More information about the freebsd-arm mailing list