junaid_ has quit [Remote host closed the connection]
aburgess has quit [Ping timeout: 255 seconds]
ldevulder has joined #riscv
junaid_ has joined #riscv
junaid_ has quit [Remote host closed the connection]
handsome_feng has joined #riscv
aburgess has joined #riscv
<drmpeg>
I thought the logo was an otter with its brain removed. :)
ezulian has quit [Quit: ezulian]
ezulian has joined #riscv
Armand has joined #riscv
random-jellyfish has joined #riscv
junaid_ has joined #riscv
junaid_ has quit [Remote host closed the connection]
hightower3 has quit [Ping timeout: 255 seconds]
hightower2 has joined #riscv
hightower2 has quit [Read error: Connection reset by peer]
hightower2 has joined #riscv
hightower2 has quit [Ping timeout: 255 seconds]
FL4SHK has quit [Server closed connection]
FL4SHK has joined #riscv
ncopa has quit [Changing host]
ncopa has joined #riscv
armand_ has joined #riscv
Armand has quit [Killed (NickServ (GHOST command used by armand_))]
armand_ is now known as Armand
hightower2 has joined #riscv
junaid_ has joined #riscv
junaid_ has quit [Remote host closed the connection]
Andre_Z has joined #riscv
yongxiang has quit [Server closed connection]
yongxiang has joined #riscv
Armand has quit [Remote host closed the connection]
Armand has joined #riscv
vagrantc has quit [Quit: leaving]
coughlanio has joined #riscv
elastic_dog has quit [Ping timeout: 245 seconds]
zjason` is now known as zjason
elastic_dog has joined #riscv
Morn_ has joined #riscv
alexghiti has joined #riscv
<Morn_>
The RISC-V unprivileged spec seems unclear to me what should be returned on DIVUW division by zero. Is is 0x00000000FFFFFFFF (Table 7.1 suggests this) or 0xFFFFFFFFFFFFFFFF (as the text "The quotient
<Morn_>
of division by zero has all bits set" says?
<sorear>
****W instructions always produce a sign-extended result, never a zero-extended one
<sorear>
supported locally as "DIVW and DIVUW are RV64 instructions that divide the lower 32 bits of rs1 by the lower 32 bits of rs2, treating them as signed and unsigned integers respectively, placing the 32-bit quotient in rd, sign-extended to 64 bits."
<sorear>
so, the second
<Morn_>
Ah, that makes sense. I guess I somehow thought of Table 7.1 as something that happens independent to sign extension, but it makes much more sense if sign extension also happens in the special cases. Thanks!
handsome_feng has quit [Quit: Connection closed for inactivity]
hightower2 has quit [Ping timeout: 255 seconds]
Tenkawa has joined #riscv
nelnire has quit [Server closed connection]
nelnire has joined #riscv
BootLayer has quit [Quit: Leaving]
<Tenkawa>
Well round one couldn't find the nvme after a chainload for some odd reason.. was very obviously devicetree related however not sure why (unless I am way off...)
<Tenkawa>
(6.6-rc booting attempt on the VF2)
<Tenkawa>
It saw everything else except the nvme from what I could tell (I'm using a chainload from microsd to boot right now so it did load the kernel)
ConorDooley is now known as conchuod
<conchuod>
The PCI stuff isn't in 6.6-rc1 though is it?
<Tenkawa>
Ah that might be a good reason why. let me see
<Tenkawa>
Well at least the base is looking good... I can build a USB only clone to start digging in
<Tenkawa>
Its there
<Tenkawa>
Symbol: PHY_STARFIVE_JH7110_PCIE [=y]
<Tenkawa>
Same as I've been using
<Tenkawa>
so unless these are just stus
<Tenkawa>
er stubs
Andre_Z has quit [Quit: Leaving.]
hightower2 has joined #riscv
<conchuod>
Ah, I was talking about the controller driver.
<Tenkawa>
what controller driver?
<Tenkawa>
there is no "controller" driver
<Tenkawa>
Not something that would be arch specific
<davidlt>
Yeah, PCIe driver didn't land in 6.6.
<davidlt>
Unless you applied the patches Linux should not see anything PCIe related.
<Esmil>
Tenkawa: PHY_STARFIVE_JH7110_PCIE is the phy driver that made it upstream, for the driver for the pcie itself (controller driver) is not upstream
<davidlt>
Ah, PHY_STARFIVE_JH7110_PCIE is a PHY driver also.
<davidlt>
Yeah, it's not enough.
<Tenkawa>
Esmil: ahhh the PHY made it but not the actual driver... makes sense
<Tenkawa>
well thats a bummer
grumbler has joined #riscv
<davidlt>
To my understanding most of PCIe is now reviewed so it most likely a v6.7 material.
<Tenkawa>
6.7? jeez
<davidlt>
Yeah, it's too late for 6.6. MW closed.
<davidlt>
I wouldn't be surprised to see some new stuff land in RC1, but that's a rare thing.
<Tenkawa>
davidlt: yeah they have dropped the ball bad on the original estimates
<davidlt>
Well, you cannot really properly estimate these things.
<Tenkawa>
(Not saying it was planned right originally)
<davidlt>
It depends on a large number of other folks.
<Tenkawa>
davidlt: I did this for a living for almost 30 years... I know
<davidlt>
The continued effort for upstream is what counts :)
<davidlt>
It's better compared to Allwinner D1 or TH1520 which gets no vendor support.
<Tenkawa>
davidlt: Don't ever say Allwinner or Rockchip around me