Finally, after months of delay, the SDcard bits have been putback^Wpushed.
This was interesting, because the SDcard bits were also some of the first bits to have been pushed into the new Mercurial tree -- and they're already in the clone. Adventurous people can start trying the code out now. Or just wait until b97.
Of course, this also means that this will be a new feature in the OpenSolaris 2008.11 release. Yay!
If you do try the bits out, let me know what works, and what doesn't. There seems to be some evidence from the Linux community that not all SDHCI compliant controllers are created equal, although the code I have works for the few variants that I've had access to.
The bugster category for bugs is solaris/driver/sdcard
Friday, August 8, 2008
Thursday, August 7, 2008
SDcard RTI submitted... webrev posted
Finally got legal approval!
A webrev is available, as well, in case anyone wants to look at it. I hope to have this integrated into b97.
A webrev is available, as well, in case anyone wants to look at it. I hope to have this integrated into b97.
Wednesday, August 6, 2008
SDcard Home Stretch
The SDcard Phase I project is in the home stretch -- the only thing remaining at this point is two signatures. And one of those is my managers! (The other one is the final sign-off from legal, which I expect to happen tomorrow.) I'll file my RTI tomorrow evening, most likely. If folks, I can also post a public webrev at the same time (though that would just be informational, as the actual required code reviews have already taken place.)
Tuesday, August 5, 2008
Classic! Another Work I Don't Care About
Apparently Twitter has been hit by another Trojan, according to the BBC.
What I love is the last paragraph in the article:
What I love is the last paragraph in the article:
Only those using Microsoft Windows are vulnerable to infection from these malicious programs.Of course, I only run Solaris at home, so I guess I have naught to fear. See, there is an upside to having a tiny market share on the desktop!
Teamware Is Dead
I still recall seeing the mail years ago, when the tools group told us that Teamware was EOL, and would not be supported any longer. I recall thinking, OMG, what are we going to do for ON? At the time, it looked (to me at least), like BitKeeper was a logical replacement.
Now here we are, years later, and with the closure of build 96 last night, we have finally stopped using Teamware for new development at Sun.
Mercurial/Cadmium seems like a powerful and capable replacement, and has the advantage of being open source. This is one of the most significant technical hurdles to fall that has kept external folks from being able to commit directly to Hg. (Opening up RTI, and the bug tracking database are the two remaining big ones. RTI can probably be opened without too much difficulty. The bug tracking problem is a different matter altogether.)
As a nice side effect, external folks can now have their changesets integrated directly, without requiring sponsors to do conversion work, and without requiring sponsors to place a "contributed by" credit. (Because the changeset will already have the contributor's e-mail.) This should significantly reduce the amount of effort required for sponsors, and consequently make it easier for more people to contribute.
Big thanks to the SCM team!
Now here we are, years later, and with the closure of build 96 last night, we have finally stopped using Teamware for new development at Sun.
Mercurial/Cadmium seems like a powerful and capable replacement, and has the advantage of being open source. This is one of the most significant technical hurdles to fall that has kept external folks from being able to commit directly to Hg. (Opening up RTI, and the bug tracking database are the two remaining big ones. RTI can probably be opened without too much difficulty. The bug tracking problem is a different matter altogether.)
As a nice side effect, external folks can now have their changesets integrated directly, without requiring sponsors to do conversion work, and without requiring sponsors to place a "contributed by" credit. (Because the changeset will already have the contributor's e-mail.) This should significantly reduce the amount of effort required for sponsors, and consequently make it easier for more people to contribute.
Big thanks to the SCM team!
Subscribe to:
Posts (Atom)