From: Christian Schrefl <chrisi.schrefl@gmail.com>
To: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>,
Jamie Cunliffe <jamie.cunliffe@arm.com>
Cc: linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
rust-for-linux@vger.kernel.org, Miguel Ojeda <ojeda@kernel.org>,
Sven Van Asbroeck <thesven73@gmail.com>
Subject: Re: [PATCH 1/1] arm: rust: Enable Rust support for ARMv7
Date: Sat, 8 Jun 2024 15:57:36 +0200 [thread overview]
Message-ID: <0a45a87f-84d1-4fb7-adaf-c612af68cd40@gmail.com> (raw)
In-Reply-To: <CANiq72kaVw_t=hCJ-qEr=9ybuOngAR6isnCK717dBEm7CFm2NQ@mail.gmail.com>
On 08.06.24 2:16 PM, Miguel Ojeda wrote:
> On Sat, Jun 8, 2024 at 12:30 AM Christian Schrefl
> <chrisi.schrefl@gmail.com> wrote:
>>
>> This is based on the code by Sven Van Asbroeck from the original
>> rust branch and inspired by the AArch version by Jamie Cunliffe.
>
> Thanks for mentioning that!
>
> (AArch64 perhaps?)
Ah yes I meant AArch64. Fixed it locally.
>> I have tested the rust samples and a custom simple MMIO module
>> on on hardware (De1SoC FPGA + Arm A9 CPU).
>
> Very nice to have tested it in real hardware, thanks!
>
> (Duplicate "on on").
I fixed that locally, but forgot to run format-patch again, sorry!
>> +``arm`` Maintained ARMv7 Little Endian only.
>
> How hard would it be to test and maintain other versions, eventually?
> I met Jamie recently, he may have some ideas here.
I think it would just be setting the correct rust target,
but I have no hardware to test it and I think its best to
only do v7 for the initial support.
>> -BINDGEN_TARGET_arm64 := aarch64-linux-gnu
>> +BINDGEN_TARGET_arm64:= aarch64-linux-gnu
>
> Spurious change?
I've changed that so the := aligns with the others, but I can
remove that for v2 if you want
>> +# Depending on how the architecute defines ARCH_SLAB_MINALIGN, bindgen might generate a binding.
>> +# Disable this here as there is a const that will always be generated in bindings_helper.c
>
> Typo in "architecute". Also, I guess you mean `.h` instead. Please use
> Markdown formatting for consistency with the rest of the file.
Fixed.
>> + panic!("arm uses the builtin rustc target");
>
> Since ARM64 puts the name of the target in the message, it would be
> nice to do the same (or perhaps it can be removed from the ARM64 one
> otherwise).
I can add the target here but then the message would have to depend
on the sub architecture if we support v6 in the future.
> Cheers,
> Miguel
next prev parent reply other threads:[~2024-06-08 13:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-07 22:30 [PATCH 1/1] arm: rust: Enable Rust support for ARMv7 Christian Schrefl
2024-06-08 12:16 ` Miguel Ojeda
2024-06-08 13:57 ` Christian Schrefl [this message]
2024-06-08 12:42 ` Geert Stappers
2024-06-10 19:00 ` Andrew Lunn
2024-06-10 19:37 ` Christian Schrefl
2024-06-10 21:19 ` Miguel Ojeda
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=0a45a87f-84d1-4fb7-adaf-c612af68cd40@gmail.com \
--to=chrisi.schrefl@gmail.com \
--cc=jamie.cunliffe@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=thesven73@gmail.com \
/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 NNTP newsgroup(s).