tag:blogger.com,1999:blog-247449072012-02-16T03:18:15.923-08:00UEFI News and CommentaryTim Lewishttp://www.blogger.com/profile/13740223047141525668noreply@blogger.comBlogger491100tag:blogger.com,1999:blog-24744907.post-67209715560003856762012-02-09T17:07:00.000-08:002012-02-09T17:07:06.042-08:00

Just read the press release blurb from Arium about their upgraded support for UEFI on their ARM products. Arium today announced support for ARM-based Unified Extensible Firmware Interface (UEFI). As part of the recently announced SourcePoint(TM) 6.9.1 debugger, Arium provides a seamless, easy-to-use, UEFI-aware development environment. Engineers have access to toolbar selections to discover

Tim Lewishttp://www.blogger.com/profile/13740223047141525668noreply@blogger.com0tag:blogger.com,1999:blog-24744907.post-50571559893730794542012-02-03T20:41:00.000-08:002012-02-05T10:29:27.987-08:00

I co-wrote (with a few Intel folks, including Vincent Zimmer who also co-wrote our book) one of the articles in the Intel Technical Journal ("UEFI Today: Bootstrapping the Continuum"). We wrote about how UEFI works to support silicon porting for firmware. My part starts on page 22, but the whole article is informative. My part details how we built up a full SMBus, ASF and DASH stack on top of the

Tim Lewishttp://www.blogger.com/profile/13740223047141525668noreply@blogger.com0tag:blogger.com,1999:blog-24744907.post-45075891290407456702012-02-03T20:35:00.000-08:002012-02-03T20:36:07.454-08:00

The next UEFI Plugfest rolls around this month on the AMD campus in Sunnyvale, CA.  If this is a typical event, and you have a Microsoft NDA, you might get a preview of the next Windows version. There is also usually a good version of Linux distros to test remote booting, including IPv6. It is free, but you must be at least a UEFI adopter to attend. Check out the registration info at www.uefi.org.

Tim Lewishttp://www.blogger.com/profile/13740223047141525668noreply@blogger.com0tag:blogger.com,1999:blog-24744907.post-58203969825279233172011-09-08T10:55:00.000-07:002011-09-08T10:55:16.708-07:00

Hey, next week, stop by the UEFI sessions and say hello. I'm speaking in EFIS003, "Beyond DOS: UEFI Modern Pre-Boot Application Development Environment" with my buddy Vincent Zimmer, who was one of my co-authors on our book about the UEFI Shell.

Tim Lewishttp://www.blogger.com/profile/13740223047141525668noreply@blogger.com0tag:blogger.com,1999:blog-24744907.post-87108331207838769822011-08-05T00:20:00.000-07:002011-08-05T00:20:04.797-07:00

I was sitting at the train station in Santa Clara and started flipping through the catalog for the UC Santa Cruz extension when I noticed, on the front cover, a computer science course with both BIOS and UEFI on the front cover. Later, when I showed this to long-time firmware engineers, they pulled out their cell-phones to take a picture. I'll post that picture later. Here's the link to the

Tim Lewishttp://www.blogger.com/profile/13740223047141525668noreply@blogger.com1tag:blogger.com,1999:blog-24744907.post-91785951347603126022011-08-04T22:09:00.000-07:002011-08-06T15:31:39.537-07:00

Front of the T-Shirt. Don't know how many people asked me if it was supposed to be an anagram for "LIFE". Well, I failed completely to talk about the UEFI summer plugfest on July 6-9, even though I was there and presented (on emulated devices). In between presentations, Intel put on some excellent training sessions on topics like the UEFI shell. See all presentations here. This event was

Tim Lewishttp://www.blogger.com/profile/13740223047141525668noreply@blogger.com1tag:blogger.com,1999:blog-24744907.post-91051897180136428972010-05-25T09:34:00.000-07:002010-05-25T09:34:22.183-07:00

I see over at http://biosism.com/ that some folks are gearing up to teach a course in "BIOS" with a focus on UEFI.

Tim Lewishttp://www.blogger.com/profile/13740223047141525668noreply@blogger.com0tag:blogger.com,1999:blog-24744907.post-34378504189508738772010-04-05T21:55:00.000-07:002010-04-05T21:55:43.478-07:00

Interesting account of folks trying to hack the IFR in a Sony Vaio to enable hidden BIOS features. I suspect we'll see a lot more of this type of thing now that much of the setup data is exposed in a format that can easily be parsed. This reminds me of what happened once ACPI became widespread and the ACPI Machine Language (AML) could be disassembled and modiifed. Some of the early virtualization

Tim Lewishttp://www.blogger.com/profile/13740223047141525668noreply@blogger.com0tag:blogger.com,1999:blog-24744907.post-43705832689373538182010-03-15T17:02:00.000-07:002010-03-15T17:08:52.093-07:00

Just received notice that there is another UEFI test workshop (see below), free for all UEFI members. I presume that means adopters, contributors and promoters. I haven't seen the note yet on the official web site yet. These workshops are really good for inter-op testing between BIOS vendors, chipset vendors, OS vendors, plug-in card vendors and UEFI software vendors. In addition, you often get

Tim Lewishttp://www.blogger.com/profile/13740223047141525668noreply@blogger.com1tag:blogger.com,1999:blog-24744907.post-3090323520131032362010-03-03T16:45:00.000-08:002010-03-03T16:45:45.307-08:00

There are a number of UEFI-related sessions at IDF this year (see http://www.intel.com/idf). Included are sessions on multi-processor, fast boot, EDK2, firmware security and cool mobile stuff for UEFI.

Tim Lewishttp://www.blogger.com/profile/13740223047141525668noreply@blogger.com0tag:blogger.com,1999:blog-24744907.post-33767953906074667752010-03-03T16:39:00.000-08:002010-03-03T16:39:49.553-08:00

The latest version of the UEFI specification (v2.3b, with updated errata) is now available here.

Tim Lewishttp://www.blogger.com/profile/13740223047141525668noreply@blogger.com3tag:blogger.com,1999:blog-24744907.post-48490014681766322802010-02-28T22:30:00.000-08:002010-02-28T22:30:40.093-08:00

The UEFI specification describes a standard set of APIs for drawing bitmaps. The HII Image protocols (as well as the Graphics Output protocol) only deal with bitmaps as arrays of 32-bit pixels. But UEFI also describes a standard way that these bitmaps (or images, as the specification calls them) should be encoded as resources (or packages).  Within the packages, images are encoded in 5

Tim Lewishttp://www.blogger.com/profile/13740223047141525668noreply@blogger.com0tag:blogger.com,1999:blog-24744907.post-22009442276586014462010-02-16T23:09:00.000-08:002010-02-16T23:09:59.920-08:00

While I was working on my project this week, I kept running into the following error: CLibApp.lib(String.obj) : error LNK2019: unresolved external symbol __allmul referenced in function _wcssize CLibApp.lib(Cwd.obj) : error LNK2001: unresolved external symbol __allmul   This function appears nowhere in my code, nor does it appear in any of the EDK's code? So what's going on? It turns out

Tim Lewishttp://www.blogger.com/profile/13740223047141525668noreply@blogger.com2tag:blogger.com,1999:blog-24744907.post-43437976156707761382010-02-12T14:57:00.000-08:002010-02-16T23:10:14.654-08:00

Last time we took a quick look at how to set up the Windows-hosted (NT32) UEFI environment provided by the EDK. The NT32 environment is very useful for debugging UEFI applications which aren't tied to specific hardware devices. So this week, I'll show how to add on debugging support. This article assumes that you have already loaded the Visual Studio project to build the EDK's NT32 platform in C

Tim Lewishttp://www.blogger.com/profile/13740223047141525668noreply@blogger.com2tag:blogger.com,1999:blog-24744907.post-51065696438095030922010-02-12T14:12:00.000-08:002010-02-16T23:10:33.655-08:00

Since I'm working on a little research project of my own using UEFI applications, I thought I'd use the Windows-hosted UEFI (aka NT32) environment provided with the EDK. From previous experience, I know that the ability to debug applications using the Visual Studio environment speeds up my development time considerably. So I thought I'd share how I set up my environment. Then next time, I'll

Tim Lewishttp://www.blogger.com/profile/13740223047141525668noreply@blogger.com5tag:blogger.com,1999:blog-24744907.post-41141455494846132822010-01-31T16:28:00.000-08:002010-02-27T20:32:24.918-08:00

Before starting, you should be aware that the term 'image' has two different meanings in UEFI. First, it refers to executables (EXE), such as drivers and applications, that get loaded into memory by the LoadImage() and StartImage() services. Second, it refers to rectangular, full-color images. Support for these images started with the UEFI 2.0 specification, with the

Tim Lewishttp://www.blogger.com/profile/13740223047141525668noreply@blogger.com0tag:blogger.com,1999:blog-24744907.post-7934884059881421312010-01-30T23:33:00.000-08:002010-01-30T23:33:40.594-08:00

Ok, now into the gory details of how font packages are encoded. In many ways, font packages are like string packages except, instead of strings, we are talking about font glyphs. There is a font header, followed by font information and then a series of font blocks. The glyph blocks represent the glyphs in sorted order, starting with the glyph for character value 0x0001 and incrementing from

Tim Lewishttp://www.blogger.com/profile/13740223047141525668noreply@blogger.com0tag:blogger.com,1999:blog-24744907.post-3078899393328776102010-01-23T20:29:00.000-08:002010-01-23T20:29:12.480-08:00

Just a quick plug to note that a book co-authored by myself and three Intel engineers (Mike Rothman, Bob Hale and Vincent Zimmer) is finally available for sale via Amazon or through Intel Press. UPS says that my personal copy arrives next Wednesday. Yeah!

Tim Lewishttp://www.blogger.com/profile/13740223047141525668noreply@blogger.com0tag:blogger.com,1999:blog-24744907.post-77020165779817030612010-01-23T20:25:00.000-08:002010-01-30T23:00:40.836-08:00

The UEFI Specification provids services and storage for manipulating bitmap fonts as part of the Human Interface Infrastructure (HII). Last week, we looked at the Simple Font, which describes a means of storing a fixed-width font for Unicode character values. Each character in the Simple Font is either in an 8 x 19 (narrow) pixel or 16 x 19 (wide) pixel character cell. Proportional fonts extend

Tim Lewishttp://www.blogger.com/profile/13740223047141525668noreply@blogger.com0tag:blogger.com,1999:blog-24744907.post-33750656088641760472009-12-06T18:20:00.000-08:002009-12-06T18:20:12.852-08:00

How do you know that the character 'A' corresponds to the character value 0x0041? Or that character value 0x215d is the character '⅝'? Well, standard, such as ASCII or the Unicode standard (or, going further back EBCDIC) describe the mapping between a numeric value and a specific characer. But how to convert those numeric values into actual bits and bytes? 7-bits, 8-bits, 16-bits, 32-bits? And

Tim Lewishttp://www.blogger.com/profile/13740223047141525668noreply@blogger.com1tag:blogger.com,1999:blog-24744907.post-2473491785600182882009-11-28T17:22:00.000-08:002010-01-30T23:00:53.776-08:00

Prior to to UEFI 2.10, there was only one graphics display mode: 800 x 600 x 32-bit color depth. Those numbers still show up as a required mode for external plug-in graphics adapters. But what if you want to draw text on those graphical displays? Where does the font come from? How big is it? Does the font really hold all 40K+ characters from the Unicode specification? According to the EFI (and

Tim Lewishttp://www.blogger.com/profile/13740223047141525668noreply@blogger.com0tag:blogger.com,1999:blog-24744907.post-79669679651956145622009-11-13T14:29:00.000-08:002009-11-13T14:29:34.449-08:00

Ok, a little promotion for the book I co-wrote, which is finally for sale. We finished writing it over 6 months ago. Not that most of you are going to run out and write UEFI Shell apps. But if you were... http://www.intel.com/intelpress/sum_eshl.htm

Tim Lewishttp://www.blogger.com/profile/13740223047141525668noreply@blogger.com0tag:blogger.com,1999:blog-24744907.post-212469241584054342009-10-26T21:54:00.000-07:002009-10-26T21:54:42.920-07:00

Last time we learned that strings in a specific language are grouped together in packages and packages are grouped together in package lists. Strings not only have text and a language, but they also have an associated font, font size and font style. To get to a specific string, you need three things: the package list handle (EFI_HII_HANDLE), the string identifier (EFI_STRING_ID) and the

Tim Lewishttp://www.blogger.com/profile/13740223047141525668noreply@blogger.com0tag:blogger.com,1999:blog-24744907.post-60530036958303451782009-10-15T22:30:00.000-07:002009-10-15T22:30:28.858-07:00

Up to this point, we've discussed the HII Database and how individual drivers can contribute resources (strings, fonts, images, forms, etc.) in the form of packages to that database. Groups of packages are called package lists. Later the form browser extracts these package lists from the database to use in constructing the user interface for platform configuration and other user-interface tasks.

Tim Lewishttp://www.blogger.com/profile/13740223047141525668noreply@blogger.com0tag:blogger.com,1999:blog-24744907.post-51953912060552813192009-10-13T23:03:00.000-07:002009-10-13T23:03:00.523-07:00

I just saw that they posted publicly the information from Intel's IDF, including the UEFI track, here. You can see a number of interesting articles from the industry heavyweights, like Dell, IBM, Microsoft and Intel. Not to mention the co-authors of a book (Vincent Zimmer, Mike Rothman) about the UEFI Shell. Good reading.

Tim Lewishttp://www.blogger.com/profile/13740223047141525668noreply@blogger.com0tag:blogger.com,1999:blog-24744907.post-31744698898112349132009-10-06T21:28:00.000-07:002009-10-07T19:11:00.561-07:00

The UEFI Human Interface Infrastructure (or HII) provides a means for drivers provided by 3rd party hardware and software vendors to expose their configuration settings. Then, a browser or provisioning application can store, restore or change those configuration settings. The configuration settings are encoded as packages. There are several different types of packages defined in the UEFI

Tim Lewishttp://www.blogger.com/profile/13740223047141525668noreply@blogger.com0tag:blogger.com,1999:blog-24744907.post-60833554667944553772009-10-03T17:09:00.001-07:002009-10-03T17:10:52.758-07:00

Several news sources have posted coverage of IDF 2009, where Phoenix (that's who I work for) booting a UEFI-based system in 1+ seconds and Windows 7 in 7-10 seconds. You can read about it (for example) here.

Tim Lewishttp://www.blogger.com/profile/13740223047141525668noreply@blogger.com0tag:blogger.com,1999:blog-24744907.post-24082030945382003402009-10-03T17:01:00.000-07:002009-10-03T17:05:22.933-07:00

Hey, just a plug for a book that I co-wrote with three other UEFI experts (Mike Rothman, Vincent Zimmer and Bob Hale) about the UEFI Shell. You can read an excerpt from the book on the Intel Press web site here.

Tim Lewishttp://www.blogger.com/profile/13740223047141525668noreply@blogger.com0tag:blogger.com,1999:blog-24744907.post-50544201237521075262009-09-26T15:36:00.000-07:002009-09-26T16:30:49.926-07:00

This week, we will look at some of the key elements of the Human Interface Infrastructure portion of the UEFI 2.1 and later specifications. UEFI platform firmware provides two key facilities:The HII Database. The database acts a repository for all sorts of configuration and user-interface resources, including forms, fonts, strings, images, animations, and keyboard layouts. The platform and

Tim Lewishttp://www.blogger.com/profile/13740223047141525668noreply@blogger.com0tag:blogger.com,1999:blog-24744907.post-48961524910313244942009-09-23T21:18:00.000-07:002009-09-23T22:15:07.235-07:00

Starting with version 2.1, the UEFI Specification began to describe a standardized way in which firmware could communicate with a user or application concerning firmware-related settings. Previously, the EFI 1.10 specification had the EFI_DRIVER_CONFIGURATION_PROTOCOL, which provided a means by which driver could take control of the console and throw up their own configuration screens. This

Tim Lewishttp://www.blogger.com/profile/13740223047141525668noreply@blogger.com0tag:blogger.com,1999:blog-24744907.post-14758960791999758212009-09-22T19:47:00.001-07:002009-09-22T20:17:51.551-07:00

Last time, I discussed how the UEFI Shell can come in four basic flavors, called support levels. Level 0 was the most basic, supporting almost all of the API, but none of the scripting language and no user interface. Level 1 added basic scripting. Level 2 added file manipulation scripting. Level 3 added user-interface related scripting. Ok. So now we have a robust shell. But it can't do very

Tim Lewishttp://www.blogger.com/profile/13740223047141525668noreply@blogger.com0tag:blogger.com,1999:blog-24744907.post-30476896471683943962009-09-07T16:11:00.001-07:002009-09-07T16:37:36.260-07:00

The UEFI shell comes in four flavors, called levels of support. These "levels" (from 0 to 3) allows for compliant implementations of the shell that range from light-weight, bare-bones to a full-featured versions. At the same time, the user of the shell can determine, at run-time, whether the necessary features are available for it to run correctly. Why offer different levels of support? Size.

Tim Lewishttp://www.blogger.com/profile/13740223047141525668noreply@blogger.com0tag:blogger.com,1999:blog-24744907.post-32855180440019611902009-09-07T15:59:00.001-07:002009-09-07T16:01:21.551-07:00

Hey, just noticed that UEFI has officially updated their roadmap here. For me, the big questions revolve around SCT support for ARM, HII and the user identification and security parts of 2.2 and 2.3. These additions are hefty (clocking in at over 300 pages).

Tim Lewishttp://www.blogger.com/profile/13740223047141525668noreply@blogger.com0tag:blogger.com,1999:blog-24744907.post-14897703933116889852007-01-04T11:07:00.000-08:002007-01-04T11:08:45.309-08:00

Hey, I just posted my wish list for 2007 drivers over at http://blogs.phoenix.com.

Tim Lewishttp://www.blogger.com/profile/13740223047141525668noreply@blogger.com0tag:blogger.com,1999:blog-24744907.post-52555221287714885952006-12-21T11:59:00.000-08:002007-01-04T11:07:37.332-08:00

A really interesting book I picked up a few months ago is called "Teach What You Know" by Steve Trautman. It is designed for technical experts who have to educate their peers while still getting their day job done. Sounds like me, since I am the only one at my office, am the chief architect for my product and the conduit for a lot of knowledge coming from other companies. It covers topics such

Tim Lewishttp://www.blogger.com/profile/13740223047141525668noreply@blogger.com0tag:blogger.com,1999:blog-24744907.post-70211880535115398232006-12-15T09:00:00.000-08:002006-12-15T09:10:20.032-08:00

There was a pretty good turn-out. The Intel site looks like it was set up for this sort of thing...five years ago. There are about 20 individual large cubes with high walls and lockable doors. Not perfectly secure, but enough to deter. The event ended up filling not only those 20 cubes but also overflowing into neighboring areas. There are no bathrooms right nearby. The conference rooms are

Tim Lewishttp://www.blogger.com/profile/13740223047141525668noreply@blogger.com0tag:blogger.com,1999:blog-24744907.post-55352349244260685412006-12-03T20:31:00.000-08:002006-12-03T20:32:51.969-08:00

Well, there are no press releases (UEFI is notably stingy on funds), but a big UEFI Test Event is taking place 11-15 December in Dupont, WA. Why Dupont? Well, primarily because Intel has a big facility with lots of open space and they were willing to help foot the bill. And, not to be outdone, AMD kicked in some money and UEFI itself covered the rest. The test group in UEFI is sponsoring this as

Tim Lewishttp://www.blogger.com/profile/13740223047141525668noreply@blogger.com0tag:blogger.com,1999:blog-24744907.post-1161619579725181922006-10-23T09:00:00.000-07:002006-10-23T09:06:19.736-07:00

Just received my copy of Beyond BIOS: Implementing the Unified Extensible Firmware Interface with Intel's Framework. This is written by three of the regular contributors to USWG and PIWG from Intel, Vincent Zimmer (PIWG, Security SubTeam, Network Sub-Team), Mike Rothman (USWG, Configuration Sub-Team) and Bob Hale (Configuration Sub-Team), so I end up talking with them a lot. I haven't read it in

Tim Lewishttp://www.blogger.com/profile/13740223047141525668noreply@blogger.com0tag:blogger.com,1999:blog-24744907.post-1157248944926579572006-09-02T19:00:00.000-07:002006-09-02T19:02:24.926-07:00

From AMI's press release: "Proven stability, modularity and ease of porting of APTIO® are not compromised and they conform to UEFI and PIWG specifications" Wow! Since there are no PIWG specifications yet (the latest are in draft), I guess that's easy to accomplish. And this is the first time I've seen them claim UEFI 2.0 compliance (since that's the only spec released so far). I'm not even sure

Tim Lewishttp://www.blogger.com/profile/13740223047141525668noreply@blogger.com0tag:blogger.com,1999:blog-24744907.post-1157248697766969902006-09-02T18:52:00.000-07:002006-09-02T18:58:17.766-07:00

Pheww. AMI is sure putting out the press releases. This time, around supporting AMD. http://www.marketwire.com/mw/release_html_b1?release_id=159150. I suppose this is to balance out their other Intel press release (see my other post). Their drop in support is a nice accomplishment, although I can just imagine the level of hacking necessary to get it to work. But it kind of looks bad for AMD. I

Tim Lewishttp://www.blogger.com/profile/13740223047141525668noreply@blogger.com0tag:blogger.com,1999:blog-24744907.post-1157248371562104112006-09-02T18:49:00.000-07:002006-09-02T18:52:51.563-07:00

As represented here: http://www.pressmethod.com/releasestorage/9378.htm, AMI is making the most of its relationship with Intel, and is starting to do training with Intel's participation, in at least Boston and Santa Clara. They claim to have done one already in Tokyo. This is important for Intel because Intel switched to use Aptio on their mobile reference platforms, but very few of their

Tim Lewishttp://www.blogger.com/profile/13740223047141525668noreply@blogger.com0tag:blogger.com,1999:blog-24744907.post-1157248147103394142006-09-02T18:41:00.000-07:002006-09-02T18:49:07.113-07:00

I actually went to visit one of the companies which is working on the project: Nanjing Byosoft. This is the one headed by ex-Phoenix employee Kangkang Shen. I went there on the last day of my trip to China. Their focus seems to be on the embedded space and they are in some sort of in-China competition to see who will do the project with the government. They are in a small building in the

Tim Lewishttp://www.blogger.com/profile/13740223047141525668noreply@blogger.com0tag:blogger.com,1999:blog-24744907.post-1153956692843792422006-07-26T16:17:00.000-07:002006-07-26T16:31:32.856-07:00

According to this official announcement (http://www.mii.gov.cn/art/2005/12/17/art_80_1697.html) the Chinese government has started a "secure" BIOS project, apparently based on UEFI. This (computer generated) translation shows the charter of creating a "New generation of security BIOS research and development and industrial production" is given to "Software Engineering Center - Chinese Academy of

Tim Lewishttp://www.blogger.com/profile/13740223047141525668noreply@blogger.com0tag:blogger.com,1999:blog-24744907.post-1153762486019234952006-07-24T10:31:00.000-07:002006-07-24T10:34:46.083-07:00

As Reuter's mentioned here: http://biz.yahoo.com/rb/060724/ati.html?.v=7, AMD has announced the purchase of ATI. So, what does this mean for UEFI? Well, AMD is a board member and ATI is a contributor, so it bumps of ATI's ability to influence overall UEFI policy. Hopefully, it means that ATI will also agressively push the PI and UEFI silicon model for its firmware deliveries. It will be

Tim Lewishttp://www.blogger.com/profile/13740223047141525668noreply@blogger.com0tag:blogger.com,1999:blog-24744907.post-1148513653371305142006-05-24T16:26:00.000-07:002006-05-24T16:34:13.383-07:00

According to this report (http://www.vnunet.com/vnunet/news/2156867/microsoft-promises-bios) from WinHEC, Microsoft will begin supporting UEFI officially with the Vista SP1 and Longhorn Server. This is actually consistent with what they said at this year's Intel IDF. However, their previous statements were so careful that many people felt Microsoft was going to pull support entirely (see the

Tim Lewishttp://www.blogger.com/profile/13740223047141525668noreply@blogger.com0tag:blogger.com,1999:blog-24744907.post-1148494995475826772006-05-24T11:10:00.000-07:002006-05-24T11:23:15.490-07:00

Insyde (as reported here: http://www.tmcnet.com/usubmit/2006/05/22/1658081.htm) put put out a press-release talking about their support of Framework support of AMD processors. They demo'd this at WinHEC running Vista. It wasn't clear whether they actually booted Vista using UEFI or using good ol' INT 19. This is important for Insyde, since they've primarily been living off of PEI/DXE drivers from

Tim Lewishttp://www.blogger.com/profile/13740223047141525668noreply@blogger.com0tag:blogger.com,1999:blog-24744907.post-1144703409372115342006-04-10T13:56:00.000-07:002006-04-10T14:10:16.873-07:00

Apple announced here (http://www.apple.com/macosx/bootcamp/) that they can now dual-boot Windows XP and MAC OS. This had previously been done via a hacker patch, but an officially supported one is quite an impressive accomplishment. What isn't clear is where they got their CSM, since XP still uses all of the legacy interrupts to boot, it means they had to stick something on the front of the DXE

Tim Lewishttp://www.blogger.com/profile/13740223047141525668noreply@blogger.com0tag:blogger.com,1999:blog-24744907.post-1143337756674050922006-03-25T17:10:00.000-08:002006-03-25T17:49:16.686-08:00

According to this article at eWeek (http://www.eweek.com/article2/0,1895,1937668,00.asp), Microsoft's initial release of Vista won't support EFI. I wasnt' actually at the IDF presentation where Andrew Ritz said this, but I was in one of the UEFI meetings running in the Marriott next door to listen to the aftermath discussion. Quite a stir, I guarantee. So the real question becomes: what does

Tim Lewishttp://www.blogger.com/profile/13740223047141525668noreply@blogger.com0tag:blogger.com,1999:blog-24744907.post-1143331330209879362006-03-25T16:00:00.000-08:002006-03-25T16:02:10.220-08:00

My name is Tim Lewis and I'm the UEFI board representative for Phoenix Technologies. This blog represents my on-going commentary on UEFI-related events and news. These opinions, of course, are my own, and do not represent those of my employer.

Tim Lewishttp://www.blogger.com/profile/13740223047141525668noreply@blogger.com0