hme/qfe x86 and SPARC binaries

hme (and by extension qfe) cards can be used on x86 systems if you download the test driver that I've supplied. Just download, extract, and follow the directions in the README file.

I'm also interested in verification that the driver performs properly on SPARC; binaries are in the same archive. The code was significantly simplified, and I need to know it works properly.

Finally, I'm seriously in need of code reviewers. I can't integrate the changes without a proper review. If you can volunteer to help, check out the webrev that I have posted.

Thanks!

(Note: on x86 qfe cards will show up as "hme" devices... this is normal and expected. The "qfe" name is an artifact only found on SPARC systems for historical reasons... the actual qfe card consists of 4 hme devices behind a PCI bridge.)

Comments

solarisuser said…
Howdy,

Is this intended to work on OpenSolaris only? I am in the process of porting our software from Solaris SPARC to Solaris x86/x64. We have lots of qfe cards in our SPARC servers - was hoping I could load up a spare qfe card on my Intel server running Solaris 10.

I found your blog on a google search just a few minutes ago.

(I realize that this is untested/unreviewed code and etc. - this is just for our development lab not for stuff we put into production)

May 6 14:20:41 msclab08 unix: /kernel/drv/hme: undefined symbol
May 6 14:20:41 msclab08 unix: 'pci_config_put8'
May 6 14:20:41 msclab08 unix: /kernel/drv/hme: undefined symbol
May 6 14:20:41 msclab08 unix: 'pci_config_get8'
May 6 14:20:41 msclab08 unix: /kernel/drv/hme: undefined symbol
May 6 14:20:41 msclab08 unix: 'ddi_quiesce_not_supported'
May 6 14:20:41 msclab08 unix: WARNING: mod_load: cannot load module 'hme'

Would compiling from source help & be feasible? Would sure beat having to go out and buy all new cards for our intel boxes.
May 6, 2009 at 12:28 PM
Unknown said…
Recompiling from source might help. I can't *promise* it will work -- there have been changes to the MAC interfaces, and its quite likely that some actual source changes will be needed.

That said, it wouldn't be *too* hard to make such changes if there was a compelling need.
May 6, 2009 at 12:30 PM
Post a Comment

Popular posts from this blog

SP (nanomsg) in Pure Go

I'm pleased to announce that this past weekend I released the first version of my implementation of the SP (scalability protocols, sometimes known by their reference implementation, nanomsg ) implemented in pure Go . This allows them to be used even on platforms where cgo is not present.  It may be possible to use them in playground (I've not tried yet!) This is released under an Apache 2.0 license .  (It would be even more liberal BSD or MIT, except I want to offer -- and demand -- patent protection to and from my users.) I've been super excited about Go lately.  And having spent some time with ØMQ in a previous project, I was keen to try doing some things in the successor nanomsg project.   (nanomsg is a single library message queue and communications library.) Martin (creator of ØMQ ) has written rather extensively about how he wishes he had written it in C instead of C++.  And with nanomsg, that is exactly what he is done. And C is a great choice for implement
Read more

An important milestone

Yesterday, with very little fanfare, illumos passed an important milestone. This milestone was the integration of  195 Need replacement for nfs/lockd+klm This is work that I originally tasked Gordon Ross and Dan Kruchinin to work while we were colleagues at  Nexenta .  Gordon started the work, picking up bits from FreeBSD as a starting point and gluing it to the illumos entry points.  Dan continued with it, and fleshed out a lot of the skeleton that Gordon had started.  It was subsequently picked up by the engineers at Delphix , and -- after some important bug fixing work was completed -- was integrated into their product quite some time ago -- reportedly its been stable since December in their product. The reason this is such an important milestone, is two fold: First, this represents a substantial collaborative effort, involving contributions from parties across several organizational boundaries.  The level of collaboration achieved here is a win for the greater good of th
Read more

The Hand May Be Forced

Well, as you may have read , Oracle has decided that at some point very soon, we're going to lose normal regular access to the source code for OS/Net. (I.e. the Solaris kernel and supporting programs.) While I would have vastly preferred for Illumos to have a cooperative and collaborative relationship with Oracle , it appears that Oracle doesn't value this. In fact, the exact words were from the management at Oracle were as follows: Solaris is not something we outsource to others, it is not the assembly of someone else’s technology, and it is not a sustaining-only product. While I understand the need to own the technology, there are few things that could be stated that show a stronger NIH attitude than this. Its unlikely that there will ever be a way for Oracle and the greater community to have a collaborative relationship. This is a dark day for OpenSolaris -- its effectively dead now. (Its parent, Solaris, lives on however.) How unfortunate. For Oracle that is. Because
Read more