[coreboot] Intel datasheets require NDAs
gregg.drwho8 at gmail.com
Sun Oct 3 07:40:11 CEST 2010
On Sun, Oct 3, 2010 at 12:42 AM, Peter Stuge <peter at stuge.se> wrote:
> ali hagigat wrote:
>> I am afraid those unmentioned registers have a significant effect in
>> understanding the function and logic of the internal parts of the IC
>> and the standards used.
> What function, logic and standards is it you want to understand
> better? We may be able to recommend some reading material. If it is
> anything but DMI or FSB then I am actually sure that we can do so.
> And if it *is* DMI or FSB then I would be curious to know why.
> I'm not saying that it is, but if your mission is to create competing
> chipsets for Intel platforms then good luck to you, but I don't think
> you will find coreboot very helpful, specifically because Intel does
> not give out documentation freely. In that case I think you would
> have no option other than reverse engineering, and that's just a lot
> of wasted time IMO.
> As Anders pointed out - we can only actually help you if you can say
> what it is that you want to do!
>> First, one must study to know what is going on, how can i work
>> without having enough information?!
> Personally I consider it critical to learn by experimentation, or
> empirical studies if you prefer. And again, I think knowing and
> understanding are two very different things.
>> I am not going to keep on complaining but the "incomplete
>> documentation" may be added to the first page of Wiki, in
> I'm afraid I don't think that is a great idea, because I think the
> first page already has too much information.
> You did not mention if you had seen the Documentation and Datasheets
> pages on the wiki. I think that the latter page in particular might
> be a good place to note that different vendors have different policy
> about public documentation, but honestly, I think it is very obvious
> coreboot mailing list: coreboot at coreboot.org
Ali, have you mastered the art of installing any Linux distribution
onto a PC? I got started in 1999 when they were beginning to move off
of a pile of floppies for Slackware, (as described on the earlier
releases.) to one or more single CDs. It is a pretty straight forward
affair, the only issue that can surface besides configuring the
necessary services, is to setup the boot methods. I mention that here
because you did not state that either.
After that installing your needed programs, and source code for them.
This is also the way Coreboot is pulled over.
If you haven't, then please do. The commands given in the Wiki that
are necessary function for enabling us to understand your target(s)
are also especially useful. Incidentally I do not reccomend Ubuntu,
there are too many outstanding issues with it. Debian will work, up to
a particular point. SuSe will definitely work as well. Slackware
however is also perfectly suited as I have it running here.
Reason why I am bringing this up is that you have mentioned your
targets, but you haven't mentioned what you're going to be using to
build the image(s) with. Or, and this is quite significant, what your
planned activities will be.
Please also understand that the documention presented here,
http://www.coreboot.org/Datasheets provides an essential collection.
The Intel stuff is limited to the publically acessible collections
they have. The material which is given there for Intel should tell you
everything you need to know. It might even tell you what's what on the
different bridging hardware of the targets you are interested in
making use of.
Sorry group if I spoke up out of turn, but I suddenly realized that he
was in the exact same position I was in, shortly after discovering the
ancestor to this group.
Gregg C Levine gregg.drwho8 at gmail.com
"This signature fought the Time Wars, time and again."
More information about the coreboot