Page MenuHomeFreeBSD

nick (Nicholas O'Brien)
User

Projects

User Details

User Since
Sep 9 2019, 5:17 PM (30 w, 3 d)

Recent Activity

Thu, Apr 2

nick committed rS359555: riscv/sifive: add FE310 Always-on driver.
riscv/sifive: add FE310 Always-on driver
Thu, Apr 2, 12:33 AM
nick closed D24170: SiFive FE310 Always-on driver.
Thu, Apr 2, 12:33 AM · riscv

Mon, Mar 30

nick updated the diff for D24170: SiFive FE310 Always-on driver.

Use exit.

Mon, Mar 30, 6:29 PM · riscv

Tue, Mar 24

nick added a comment to D24152: RISC-V: copy the DTB to early KVA.

I haven't tested this, yet, either. It looks good though.

Tue, Mar 24, 4:02 PM
nick created D24170: SiFive FE310 Always-on driver.
Tue, Mar 24, 12:45 AM · riscv

Mon, Mar 23

nick accepted rS359218: Fix ordering of machine includes.

Looks good to me. Thanks for the cleanup!

Mon, Mar 23, 12:00 AM

Sun, Mar 22

nick accepted D24155: RISC-V: exclude reserved memory regions.
Sun, Mar 22, 11:42 PM
nick added a comment to D24155: RISC-V: exclude reserved memory regions.

Looks good to me. Thanks for this patch Mitchell!

Sun, Mar 22, 11:41 PM

Fri, Mar 20

nick committed rD54001: Add myself (nick) as a src committer.
Add myself (nick) as a src committer
Fri, Mar 20, 5:54 PM
nick closed D24129: Add myself (nick) as a src commiter.
Fri, Mar 20, 5:54 PM
nick committed rS359179: Add myself (nick) as a src committer.
Add myself (nick) as a src committer
Fri, Mar 20, 5:16 PM
nick closed D24130: Add myself (nick) as a src commiter.
Fri, Mar 20, 5:16 PM
nick updated the summary of D24129: Add myself (nick) as a src commiter.
Fri, Mar 20, 2:49 AM
nick updated the summary of D24130: Add myself (nick) as a src commiter.
Fri, Mar 20, 2:48 AM
nick created D24130: Add myself (nick) as a src commiter.
Fri, Mar 20, 12:14 AM
nick created D24129: Add myself (nick) as a src commiter.
Fri, Mar 20, 12:05 AM

Thu, Mar 12

pi renamed nick from nickisobrien_gmail.com to nick.
Thu, Mar 12, 5:06 AM

Mar 9 2020

nick added a comment to D23877: RISCV Platform Specific Code.

Hi Ruslan,

Why cpu_check_mmu() does not work for you?

There's nothing harmful in this check long term, but from what I can tell, the reason we do that check is specific to the FU540 which, in principal, in my opinion, shouldn't be in the base kernel.

Mar 9 2020, 5:58 PM · riscv
nick created D24004: SiFive/SPI: Silence build warning.
Mar 9 2020, 3:35 AM

Mar 5 2020

nick updated the diff for D23877: RISCV Platform Specific Code.
  • Silence warning if PLATFORM isn't set
  • Remove unnecessary headers in mp_machdep.c
Mar 5 2020, 11:26 PM · riscv
nick added a comment to D23877: RISCV Platform Specific Code.

Thanks for taking the time to think about it @mhorne and @philip! It's important to have these discussions. More flexibility doesn't necessarily equal "better".

One thing I think is unclear is how OpenSBI will fare when we start to see more platforms emerge. They provide a space for vendor-specific SBI extensions, and make it "easy" to port to new platforms, but we will have to see if vendors actually go for that. I think some of our kernel architecture for RISC-V will be driven by how well the SBI is adopted.

Yeah, I'm also really curious about how SBI is going to be implemented by vendors and it will undoubtedly drive our kernel development in regards to platform specificity moving forward. I'd probably prefer to see most of those "hacks" taken care of in SBI but it's not quite clear whether that's the case today.

agree with you in the general case, we don't want platform specific hacks scattered around the kernel, it's better to keep them in one location. I believe that "mmu-type" is intended to be a standard property in all RISC-V device trees going forward, and we could reliably check it for all platforms. See: https://github.com/torvalds/linux/blob/master/Documentation/devicetree/bindings/riscv/cpus.yaml

Yeah, there's nothing necessarily harmful in this check from what I can tell. And as I said, at Axiado it's not harming us, but as Philip pointed out:

Currently the default RISC-V platform smells a lot like FU540.

It's more the principal that concerns me here rather than the direct impact of this specific check. I understand that you agree with this as well.

Mar 5 2020, 9:45 PM · riscv

Mar 2 2020

nick added a comment to D23877: RISCV Platform Specific Code.

Okay, I'm not totally opposed to this interface, but I would like to better understand the motivation behind adopting it before we do so.
Does this solve a problem for some proprietary core? As I see it, this doesn't change anything for the FU540.
The arm directory is littered with these platform files, and this seems to be out of necessity due to the variety and inconsistency of standards that exists in its hardware. arm64 seems to have avoided the need for this interface so far, and I wonder if we can do the same. The Linux RISC-V world seems to be pushing hard for OpenSBI and keeping platform abstractions at the firmware level. We don't have to follow what Linux does, but I think we ought to be thoughtful in what we choose to do here. Thoughts?

Mar 2 2020, 10:28 PM · riscv
nick added a reviewer for D23877: RISCV Platform Specific Code: kp.
Mar 2 2020, 7:20 PM · riscv

Feb 29 2020

nick updated the diff for D23879: RISCV: PLATFORM_DEFAULT implementation.
Feb 29 2020, 9:05 PM · riscv
nick updated the diff for D23877: RISCV Platform Specific Code.
Feb 29 2020, 8:45 PM · riscv

Feb 28 2020

nick updated the summary of D23878: RISCV: SiFive specific platform.
Feb 28 2020, 5:42 PM · riscv
nick updated the summary of D23879: RISCV: PLATFORM_DEFAULT implementation.
Feb 28 2020, 5:42 PM · riscv
nick created D23879: RISCV: PLATFORM_DEFAULT implementation.
Feb 28 2020, 5:41 PM · riscv
nick created D23878: RISCV: SiFive specific platform.
Feb 28 2020, 5:37 PM · riscv
nick updated the summary of D23877: RISCV Platform Specific Code.
Feb 28 2020, 5:28 PM · riscv
nick created D23877: RISCV Platform Specific Code.
Feb 28 2020, 5:27 PM · riscv

Oct 15 2019

nick created D22035: Generalize ARM specific comments in devmap.
Oct 15 2019, 12:43 AM

Oct 12 2019

nick added a comment to D21998: RISC-V: Call devmap_print_table() on bootverbose.

While you're at it, it would be helpful to fix the dated arm-specific comments in subr_devmap.c. ;-)

Oct 12 2019, 5:52 PM
nick updated the summary of D21998: RISC-V: Call devmap_print_table() on bootverbose.
Oct 12 2019, 5:50 PM
nick created D21998: RISC-V: Call devmap_print_table() on bootverbose.
Oct 12 2019, 5:36 PM

Oct 10 2019

nick updated the diff for D21975: RISC-V: Call devmap_bootstrap().

Fix the header order (alphabetical)

Oct 10 2019, 9:21 PM
nick updated the diff for D21975: RISC-V: Call devmap_bootstrap().
Oct 10 2019, 9:19 PM
nick created D21975: RISC-V: Call devmap_bootstrap().
Oct 10 2019, 8:34 PM

Sep 9 2019

nick created D21576: Small fix to CPU Compatibility Identification.
Sep 9 2019, 6:24 PM