1 |
On Wed, Jun 20, 2012 at 05:56:28PM -0400, Richard Yao wrote: |
2 |
> On 06/20/2012 04:13 PM, Richard Yao wrote: |
3 |
> >> Stop right there. That's just not going to happen, sorry. You aren't |
4 |
> >> going to be able to get a user to replace their BIOS, nor should you |
5 |
> >> ever want to. You are not going to be able to keep up with the |
6 |
> >> hundreds, if not thousands, of different motherboards being introduced |
7 |
> >> every month, in order to just get rid of the secure boot option. |
8 |
> > |
9 |
> > OpenWRT does that with routers and Cyanogenmod does that with phones. It |
10 |
> > seems reason for us to offer it as an option to users. With that said, |
11 |
> > this probably won't happen. One of the Core Boot developers informed me |
12 |
> > of what is involved in setting up the address space and it is infeasible |
13 |
> > for us to do. |
14 |
> |
15 |
> From what I can tell, the Core Boot developers could use that |
16 |
> documentation. You yourself said "If there's anything that anyone is |
17 |
> thinking I should be doing but seem not to be, please let me know.". Do |
18 |
> you have any intention of acting on that?a |
19 |
|
20 |
Getting documentation from Intel without an NDA is not something that it |
21 |
is possible for me to do, sorry. The coreboot developers have much |
22 |
better contacts in this area (hint, I have none.) |
23 |
|
24 |
greg k-h |