Page MenuHomeFreeBSD

smartpqi: update to version 4410.0.2005
ClosedPublic

Authored by john.hall_microchip.com on Aug 22 2023, 3:16 PM.
Tags
None
Referenced Files
Unknown Object (File)
Mon, Oct 28, 4:45 AM
Unknown Object (File)
Sun, Oct 13, 1:48 PM
Unknown Object (File)
Sun, Oct 13, 1:48 PM
Unknown Object (File)
Sun, Oct 13, 1:48 PM
Unknown Object (File)
Sun, Oct 13, 1:47 PM
Unknown Object (File)
Sun, Oct 13, 1:47 PM
Unknown Object (File)
Sun, Oct 13, 1:47 PM
Unknown Object (File)
Sun, Oct 13, 1:46 PM
Subscribers

Details

Summary

This updates the source of the smartpqi driver to the latest release 4410.0.2005.

Diff Detail

Repository
rG FreeBSD src repository
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

john.hall_microchip.com created this revision.
john.hall_microchip.com created this object with visibility "Custom Policy".
john.hall_microchip.com created this object with edit policy "Custom Policy".
john.hall_microchip.com added a reviewer: imp.
john.hall_microchip.com changed the visibility from "Custom Policy" to "Custom Policy".
john.hall_microchip.com changed the edit policy from "Custom Policy" to "Custom Policy".

So this generally looks good. Left a couple of comments
But since this is mostly managed by microchip, maybe it should be in sys/contrib/dev/smartpqi to indicate that? Thoughts?
I can't really commment on the bulk of these changes, since they are very dependent on the hardware that I'm unfamiliar with.

share/man/man4/smartpqi.4
29

We just removed all $FreeBSD$ from the tree... Here and below...

sys/modules/smartpqi/Makefile
6

this likely won't work in the FreeBSD tree.

8

We've been trying to do these as one per line...

Not sure what sys/contrib/dev would buy us. We would want the driver in the kernel so doesn't it have to be in sys/dev ?

Not sure what sys/contrib/dev would buy us. We would want the driver in the kernel so doesn't it have to be in sys/dev ?

sys/contrib/dev buys two things (and doesn't do one thing you think)

  1. It turns off a number of formatting and pedantic requirements for formatting. This will become increasingly more important as time rolls on and the FreeBSD project tries to get more in line with other projects.
  2. You can use a 'vendor tree' to merge in your vendor changes. This lets you more easily manage the diffs that FreeBSD has added to keep the driver up to date with the latest APIs between imports from the vendor.

It does not mean it won't be in the GENERIC kernel. That's controlled via a different mechanism.

It's also just a suggestion based on microchip's recent publication of its latest linux driver on github.

In D41550#946927, @imp wrote:

Not sure what sys/contrib/dev would buy us. We would want the driver in the kernel so doesn't it have to be in sys/dev ?

sys/contrib/dev buys two things (and doesn't do one thing you think)

  1. It turns off a number of formatting and pedantic requirements for formatting. This will become increasingly more important as time rolls on and the FreeBSD project tries to get more in line with other projects.
  2. You can use a 'vendor tree' to merge in your vendor changes. This lets you more easily manage the diffs that FreeBSD has added to keep the driver up to date with the latest APIs between imports from the vendor.

It does not mean it won't be in the GENERIC kernel. That's controlled via a different mechanism.

It's also just a suggestion based on microchip's recent publication of its latest linux driver on github.

Sounds interesting. We will keep this in mind for future projects. As for now let's just keep it in sys/dev .

Are we in time to get this added? Any one else we should have look this over?

OK. I'll commit this, assuming it builds. that should make it under the wire for 14.0. And I'll not plan on MFCing this, per earlier discussions.

Look forward to future moves of the driver, but agree it might be a smidge late to do that now.

This revision was not accepted when it landed; it landed in state Needs Review.Aug 24 2023, 9:30 PM
This revision was automatically updated to reflect the committed changes.
john.hall_microchip.com changed the visibility from "Custom Policy" to "Public (No Login Required)".Aug 29 2023, 4:38 PM