From: Bryan Hundven <bryanhundven@gmail.com>
To: mike@raspberryvi.org
Cc: crossgcc@sourceware.org
Subject: Re: [crosstool-ng/crosstool-ng] bc9ed3: Adds Raspberry Pi 3 sample config
Date: Thu, 03 Mar 2016 15:58:00 -0000 [thread overview]
Message-ID: <5F16F837-8600-46CD-9267-34C06E615BB4@gmail.com> (raw)
In-Reply-To: <56D85DBB.5040802@raspberryvi.org>
[-- Attachment #1: Type: text/plain, Size: 5348 bytes --]
> On Mar 3, 2016, at 7:52 AM, Mike Ray <mike@raspberryvi.org> wrote:
>
> Hello Bryan.
>
> I'll see if I can tweak the config myself at the same time. But because
> I'm blind I don't find menuconfig (or other curses apps) all that easy
> to use. Incidentally apologies for top-posting but that's another thing
> with not being able to see...and a bit lazy.
I think the toolchain built here should work fine, I’m just saying that the platform itself might need a little love. When I get my rpi3, I’ll definitely be wanting to running the test-suite on it asap.
>
> But there's plenty of ARM Cortex A53 stuff online so I might be able to
> just use one of the other configs to hack it.
>
> Mike
PS: it’s hard to keep context of the message when you top post. Please don’t top post. :)
https://en.wikipedia.org/wiki/Posting_style
>
> On 03/03/2016 15:19, Bryan Hundven wrote:
>>
>>> On Mar 3, 2016, at 4:45 AM, Bryan Hundven <bryanhundven@gmail.com> wrote:
>>>
>>>
>>>> On Mar 2, 2016, at 10:23 PM, Mike Ray <mike@raspberryvi.org> wrote:
>>>>
>>>> Hello.
>>>>
>>>> Good to know it's not just me being an idiot! I was hoping to use a
>>>> toolchain generated with ct-ng to build a 64-bit root file-system using
>>>> buildroot or just using the toolchain with cross-LFS.
>>>
>>> Indeed! That’s the spirit! :)
>>>
>>>>
>>>> I will continue to tinker and at the same time wait to see if there are
>>>> changes to this sample.
>>>
>>> There may only be one change to the sample, one line added, but the real change will happen in two files (maybe 3). And really, they aren’t big changes.
>>>
>>>>
>>>> It's true that at the moment there are only 32-bit images available. I
>>>> expect ArchARM to come up with a 64-bit image soon enough though.
>>>
>>> Indeed, but someone has to push the edge and give it a go?
>>>
>>> I need to get myself a PI3. I have to wait till the 15th to order mine, but that doesn’t mean I can’t start getting ct-ng there. I know there are others out there waiting for aarch64 support, so let’s do this.
>>>
>>>>
>>>> Mike
>>>
>>> Cheers,
>>>
>>> -Bryan
>>
>> Well, I feel like I totally missed the mark yesterday. I didn’t realize RPI3 was a 64-bit cpu, and I assumed ct-ng did not have aarch64 support. 0/2…
>>
>> On the plus side, I have something to test:
>> https://github.com/crosstool-ng/crosstool-ng/pull/362
>>
>> Now, the hard part. You can’t run 64-bit binaries on 32-bit.
>> Also, I’m not sure if you can boot aarch64 from a 32-bit bootloader?
>> So you may have to start with making u-boot?
>>
>> I wish I had an RPI3, so I could help with that, but for now I’ll just have to be patient and wait to hear your progress. If you do make progress, and need help, post a git repo somewhere and I’ll try to help if I can.
>>
>> -Bryan
>>
>>>
>>>>
>>>>
>>>> On 03/03/2016 00:28, Stefan Hallas Mulvad wrote:
>>>>> Hi Bryan,
>>>>>
>>>>> I did test this, but at this time there’s (to my knowledge) no os images available which supports 64 bit. Mine came with 32 bit raspbian,
>>>>>
>>>>> The chip is capable of running in both 32/64 bit mode - but 64 bit must come down the road as software becomes available.
>>>>>
>>>>> Best regards,
>>>>> Stefan Mulvad
>>>>>
>>>>>
>>>>>> On Mar 2, 2016, at 4:22 PM, Bryan Hundven <bryanhundven@gmail.com> wrote:
>>>>>>
>>>>>> Hello Mike,
>>>>>>
>>>>>>
>>>>>>> On Mar 2, 2016, at 3:51 PM, Mike Ray <mike@raspberryvi.org> wrote:
>>>>>>>
>>>>>>> Hello.
>>>>>>>
>>>>>>> I have used this sample to build a toolchain.
>>>>>>>
>>>>>>> However I get 32-bit executables and the '-m64' switch is not recognized.
>>>>>>
>>>>>> Sometimes, I expect that when people open pull-requests that they actually test what they submit and I don’t have to do any work.
>>>>>>
>>>>>> Today I failed at that. Yeay!
>>>>>>
>>>>>> Arm64/aarch64 is kind of a new thing in crosstool-NG, and isn’t well supported.
>>>>>>
>>>>>> I took the pull-request for the sample without looking at the specs for the new raspberry pi 3. I had no clue it was 64-bit.
>>>>>>
>>>>>> Looks like I will have to take some time and get this going.
>>>>>>
>>>>>>>
>>>>>>> There is obviously a gap in my knowledge which I can't seem to find an
>>>>>>> answer for on Google.
>>>>>>>
>>>>>>> Can I compile a 64-bit executable? If so, how?
>>>>>>>
>>>>>>> Thanks for any help.
>>>>>>>
>>>>>>> Mike
>>>>>>>
>>>>>>>
>>>>>>
>>>>>> Thanks for reporting this issue!
>>>>>>
>>>>>> https://github.com/crosstool-ng/crosstool-ng/issues/361
>>>>>>
>>>>>> Cheers,
>>>>>>
>>>>>> -Bryan
>>>>>
>>>>
>>>>
>>>> --
>>>> Michael A. Ray
>>>> Analyst/Programmer
>>>> Witley, Surrey, South-east UK
>>>>
>>>> Eyes-free Linux:
>>>> http://eyesfreelinux.ninja/
>>>>
>>>> Raspberry VI:
>>>> http://www.raspberryvi.org/
>>>>
>>>>
>>>> --
>>>> For unsubscribe information see http://sourceware.org/lists.html#faq
>>>>
>>>
>>
>
>
> --
> Michael A. Ray
> Analyst/Programmer
> Witley, Surrey, South-east UK
>
> Eyes-free Linux:
> http://eyesfreelinux.ninja/
>
> Raspberry VI:
> http://www.raspberryvi.org/
>
>
> --
> For unsubscribe information see http://sourceware.org/lists.html#faq
>
[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 496 bytes --]
next prev parent reply other threads:[~2016-03-03 15:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-02 20:11 Bryan Hundven
2016-03-02 23:51 ` Mike Ray
2016-03-03 0:23 ` Bryan Hundven
2016-03-03 0:28 ` Stefan Hallas Mulvad
2016-03-03 6:23 ` Mike Ray
2016-03-03 12:45 ` Bryan Hundven
2016-03-03 15:19 ` Bryan Hundven
2016-03-03 15:52 ` Mike Ray
2016-03-03 15:58 ` Bryan Hundven [this message]
2016-03-03 0:25 ` Stefan Hallas Mulvad
2016-03-10 21:20 ` Thomas Petazzoni
2016-03-11 2:06 ` Bryan Hundven
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=5F16F837-8600-46CD-9267-34C06E615BB4@gmail.com \
--to=bryanhundven@gmail.com \
--cc=crossgcc@sourceware.org \
--cc=mike@raspberryvi.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).