Re: Regular QEMU RISC-V Call

On Wed, 22 Jul 2026, at 5:02 AM, Daniel Henrique Barboza wrote:
> 
> 
> On 7/21/2026 3:37 PM, Alistair Francis wrote:
> > On 17/6/26 09:18, Alistair wrote:
> >> On Tue, 16 Jun 2026, at 8:35 PM, Alistair Francis wrote:
> >>> On 16/6/26 16:07, Joel Stanley wrote:
> >>>> On Thu, 11 Jun 2026 at 13:52, Alistair <[email protected]> wrote:
> >>>>> For the time, I'm picking Wednesday the 17th of June at 10AM AEST (UTC+10). Hopefully that works ok for everyone. If it doesn't let me know and we might be able to move it around.
> >>>
> >>> That means the meeting should start in a little less then 13 and a half
> >>> hours! I'll send out a Teams invite tomorrow
> > 
> > Hey!
> > 
> > I realised that it's now been a month. I leave for holidays in a few days, am currently recovering from some sickness and don't have any agenda items. So let's skip this month and start again in August
> 
> In fact the meeting was yesterday according to the calendar invite Palmer sent
> :D figured that ppl forgot about it and I dropped the call after 10 minutes.
> 
> If we're going to stick with Palmer's existing invite the next meeting will be
> August 18th 10AM UTC+10.

My Teams meeting thing had the 17th of August.

I only get back on the 17th, so let's do the Thursday the 17th at the same time.

So 2 days later then Palmers event. Does that work?

> 
> As an agenda for next call I have a couple of topics:
> 
> - ongoing Debug related work.  Hopefully we'll have some Debug 0.13/1.0 patches
> under review by that date;

I see them. Hopefully by then I can review them.

Alistair

> - there is a chance that common efforts led by ARM folks (single binary, multi accel ..)
> will spill in the RISC-V tree.  I'll talk with Phil and Pierrick later this week and see
> if there's something to do on our side.
> 
> 
> Cheers,
> Daniel
> 
> 
> > 
> > Alistair
> > 
> >>
> >> Call in details are below. Starting in 40 minutes!
> >>
> >> ________________________________________________________________________________
> >> Microsoft Teams meeting
> >>
> >> Join:
> >> https://teams.microsoft.com/meet/275503449279724?p=C2D0EDrqxwFb5LuRnB
> >>
> >> Meeting ID:
> >> 275 503 449 279 724
> >>
> >> Passcode:
> >> kS9Vg23i
> >>
> >> ________________________________________
> >> Need
> >>   help? |
> >> System reference
> >> Dial in by phone
> >>
> >> +1
> >>   408-627-4258,,498330396#
> >> United States, San Jose
> >> Find
> >>   a local number
> >> Phone conference ID:
> >> 498 330 396#
> >>
> >> Join on a video conferencing device
> >>
> >> Tenant key:
> >> [email protected]
> >>
> >> Video ID:
> >> 119 833 426 2
> >>
> >> More
> >>   info
> >> For organizers:
> >> Meeting
> >>   options |
> >> Reset dial-in PIN
> >>
> >> ________________________________________________________________________________
> >>
> >>>
> >>>>
> >>>> I'll be on, hopefully in the right timezone this time around. 9:30 ACST.
> >>>>
> >>>>> If anyone has anything they want to discuss let me know. I can send an agenda and confirmed meeting time out in a few days.
> >>>>
> >>>> Two agenda items:
> >>>>
> >>>> * RISC-V Code Policy
> >>>>
> >>>> https://lore.kernel.org/qemu-riscv/[email protected]/
> >>>>
> >>>> Good idea writing down your expectations somewhere everyone can see.
> >>>> Do you want to raise it as a topic and we can talk it through?
> >>>
> >>> Yep!
> >>>
> >>>>
> >>>> * Machine model use cases
> >>>>
> >>>> I wanted to share my perspective on the system emulator machines, what
> >>>> they are for, who they are for, and hear what others had to say.
> >>>
> >>> Sounds good as well
> >>>
> >>> Alistair
> >>>
> >>>>
> >>>> See you on the call tomorrow.
> >>>>
> >>>> Cheers,
> >>>>
> >>>> Joel
> >>>
> >>>
> > 
> 
>