[coreboot] compiling coreboot

Corey Osgood corey.osgood at gmail.com
Sat Jul 24 16:34:32 CEST 2010


On Sat, Jul 24, 2010 at 2:03 AM, ali hagigat <hagigatali at gmail.com> wrote:
> My motherboard will be Kontron, 986LCD-M/mITX.

Good grief. That board is already supported!

http://www.coreboot.org/Kontron_986LCD-M_mITX

-Corey

>
> I have not yet received it but very soon will have it. I am studying the
> technical info but answering my questions boosts my progress.
>
> I am not planing to make a product for sale and trying to expand my
> knowledge about BIOS and PC. I have a good time to spend for this project
> but seems to have to learn many new things first and deal with some PDFs
> every day.
>
>
> On Wed, Jul 21, 2010 at 5:53 PM, Corey Osgood <corey.osgood at gmail.com>
> wrote:
>>
>> I think I just need to clarify a couple things:
>>
>> On Wed, Jul 21, 2010 at 8:19 AM, Corey Osgood <corey.osgood at gmail.com>
>> wrote:
>> > On Wed, Jul 21, 2010 at 8:06 AM, ali hagigat <hagigatali at gmail.com>
>> > wrote:
>> >> My first impression from the BIOS open source project was an effort to
>> >> expand knowledge not to earn money!!
>>
>> There are lots of reasons open-source projects thrive. Most of them
>> involve money. Why are you working with coreboot? Is it (just a guess)
>> because you're developing a product to sell?
>>
>> >>
>> >> If any one wants to earn money he will find a technical job, will get
>> >> involved in deadlines of the project, will tolerate the pressure and
>> >> stress
>> >> of a challenging and rewarding work.
>>
>> Yeah, paying people to teach? What a ridiculous idea!
>>
>> >>
>> >> I thought we were here to help each other to understand the details of
>> >> the
>> >> science and technology involved and become ready to invent something
>> >> new or
>> >> to become ready for the projects in the market.
>>
>> And if you come on here with a *technical* issue, e.g. need a hand
>> initiating an HT link, memory controller, ide device, kernel errors,
>> etc, then the people on here will bend over backwards to help you out.
>> On the other hand, documentation exists for a reason, because we don't
>> have time to explain every line of code to every person who comes
>> along.
>>
>> >>
>> >> Though spending money for this case seems contrary to the first
>> >> purposes of
>> >> the project but money might be paid to responsible and eligible
>> >> technical
>> >> people. Who you recommend and where are those?
>>
>> http://www.coreboot.org/Products
>> http://www.google.com/search?q=coreboot+professional+development
>>
>> >>
>> >> I am ready to develop code for Coreboot but my knowledge is not enough
>> >> and I
>> >> suspect the knowledge of many users of this mailing list to be enough
>> >> for
>> >> it!!
>>
>> I really don't think that's the case. Read the mailing list archives,
>> how many questions do you see like yours?
>>
>> Alright, because I'm just plain too damn nice to leave it at this, if
>> you're still interested, what board/chipset are you working on? I'll
>> get you pointed in the right direction. I'm not going to explain how
>> every piece of coreboot works, but you really don't need to know to
>> write a working port.
>>
>> -Corey
>>
>> >
>> > Look dude, I'm getting tired of this nonsense. All the info you need
>> > is in the wiki and the documentation. How do I know? coreboot is one
>> > of the few projects I've gotten involved in. I'm not a professional
>> > developer, not even a great programmer. I don't build CPUs for a
>> > living, hell I don't even pretend to fully comprehend how everything
>> > works. Yet when I started with this project, I found all the info I
>> > needed to get started. And I've worked my way through to port a couple
>> > 440bx boards, the i810 chipset, and the cn700 chipset (albiet that one
>> > was left a little incomplete due to the untimely death of my cn700
>> > board). If you're not willing to make the effort to find *basic* info,
>> > why the heck should we waste our time spoon feeding it to you? Because
>> > if you're not willing to make that little effort, you're probably not
>> > going to put in the effort to actually write the code, make it work,
>> > and contribute it back to the project.
>> >
>> > So, to reiterate carl-daniel's points:
>> > 1. Put forth the effort yourself to learn about the project
>> > 2. Pay someone to make it worth their while to spend their time
>> > educating you, rather then working on projects of their own, or
>> > 3. GTFO!
>> >
>> > -Corey
>> >
>> >>
>> >> On Wed, Jul 21, 2010 at 3:56 PM, Carl-Daniel Hailfinger
>> >> <c-d.hailfinger.devel.2006 at gmx.net> wrote:
>> >>>
>> >>> Hi,
>> >>>
>> >>> let me explain a few things.
>> >>>
>> >>> On 21.07.2010 12:16, ali hagigat wrote:
>> >>> > The reason some of you do not like to answer is not lack of time. It
>> >>> > is
>> >>> > because you do not want other people know about the details of the
>> >>> > project,
>> >>> >
>> >>>
>> >>> We will tell you about the details of our project if you are friendly
>> >>> and if you read the documentation.
>> >>>
>> >>>
>> >>> > Rudolf, answering my questions take you not more than a few minutes
>> >>> > of
>> >>> > your
>> >>> > time and it is not a waste of time. Answering technical questions
>> >>> > are
>> >>> > not a
>> >>> > waste of time, never, as it is a kind of practice and helps people
>> >>> > keep
>> >>> > their knowledge updated or refreshed. I did not ask you about
>> >>> > economics,
>> >>> > politics and the subjects unrelated to computer science, how can i
>> >>> > waste
>> >>> > your time? It is something you can benefit from if you think about
>> >>> > it
>> >>> > unless
>> >>> > you have other reasons (that I am aware of!!)
>> >>> >
>> >>>
>> >>> We do not benefit from explaining things to you.
>> >>> You have shown an unwillingness to learn independently, so the project
>> >>> does not benefit from explaining things to you either.
>> >>> BUT... if you pay some of us _enough_ money, they will treat you as a
>> >>> customer and explain things to you even if you are unwilling to do any
>> >>> work yourself.
>> >>>
>> >>> Even if you promised to help us with developing coreboot, we would not
>> >>> benefit until the amount of development done by you saves other
>> >>> developers more time than they lose explaining things to you. We do
>> >>> not
>> >>> know you, and we have no way to make sure if you really intend to help
>> >>> or if you're just trolling. Your behaviour so far is pretty close to
>> >>> trolling.
>> >>>
>> >>>
>> >>> > I asked some questions to understand the overall framework of the
>> >>> > work
>> >>> > without going into the details. I knew about the wiki site of
>> >>> > Coreboot
>> >>> > before, how could i register at this mailing list while I found it
>> >>> > by
>> >>> > Coreboot site!!?
>> >>> >
>> >>>
>> >>> Apparently you found the wiki, but you're unwilling or unable to read
>> >>> and understand the main contents, and focused on the mailing list
>> >>> instructions instead.
>> >>>
>> >>>
>> >>> > Go read wiki or the source code are the solutions I knew myself, i
>> >>> > have
>> >>> > the
>> >>> > source and the Internet connection...
>> >>> >
>> >>>
>> >>> And why don't you do that?
>> >>>
>> >>> You have three choices:
>> >>> 1. Be friendly. Read the source/documentation. We'll explain the rest.
>> >>> 2. Pay someone to explain this in private.
>> >>> 3. Leave.
>> >>>
>> >>>
>> >>> Regards,
>> >>> Carl-Daniel
>> >>
>> >>
>> >> --
>> >> coreboot mailing list: coreboot at coreboot.org
>> >> http://www.coreboot.org/mailman/listinfo/coreboot
>> >>
>> >
>
>
> --
> coreboot mailing list: coreboot at coreboot.org
> http://www.coreboot.org/mailman/listinfo/coreboot
>




More information about the coreboot mailing list