-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 09/21/2017 04:52 PM, Kyösti Mälkki wrote:
Hi Kyösti,
>
> I can help you to get these to EARLY_CBMEM_INIT. That's the first
> obstacle with Geode. It's recommended that coreboot would store
> the timebase / TSC information so that cpufreq
On Thu, Sep 21, 2017 at 10:16 AM, David Hendricks
wrote:
>
>
> On Sun, Sep 10, 2017 at 1:42 PM, Piotr Król wrote:
>>
>> 2. Is cbmem required ? (Geode LX do not have support for cpufreq -
>> cbmem complains)
>
I can help you to get these to
On Sun, Sep 10, 2017 at 1:42 PM, Piotr Król wrote:
> 2. Is cbmem required ? (Geode LX do not have support for cpufreq -
> cbmem complains)
>
Yes, though hopefully we can patch cbmem to deal with this. I am only
guessing but it seems it will fail in arch_tick_frequency()?
On Fri, Aug 25, 2017 at 4:41 PM, David Hendricks
wrote:
> On Thu, Aug 24, 2017 at 11:12 AM, Renze Nicolai wrote:
>
>> Another thing: I don't understand the workflow for putting my
>> boardstatus on the wiki yet. Could someone explain to me how I can
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 08/24/2017 04:31 AM, Kyösti Mälkki wrote:
> On Thu, Aug 24, 2017 at 12:29 AM, taii...@gmx.com
> wrote:
Hi Kyösti,
(...)
>
> Now, this applies to everyone: please push status updates for the
> boards you have access to,
On Thu, Aug 24, 2017 at 11:12 AM, Renze Nicolai wrote:
> Another thing: I don't understand the workflow for putting my
> boardstatus on the wiki yet. Could someone explain to me how I can
> publish on the wiki that my board works with a certain version of
> Coreboot? Also: how
Hello everyone,
A year ago I ported coreboot to the motherboard (MSI MS7721) that I use
in my main PC. In my opinion removing support for boards that are
actively used by people in this community would be a setback for the
project as a whole.
While I currently don't have the time and knowledge
On Wed, Aug 23, 2017 at 7:00 AM, taii...@gmx.com wrote:
> Just because a board lacks active developers doesn't mean that no one is
> using it.
> As a layman I simply can't understand as to how all these seemingly
> insignificant improvements such as CBMEM in ramstage make it
On Wed, Aug 23, 2017 at 8:31 PM, Kyösti Mälkki wrote:
> On Thu, Aug 24, 2017 at 12:29 AM, taii...@gmx.com wrote:
>> Ah I see thanks for explaining.
>>
>> I had read all the AGESA boards were going to be removed, besides the asus
>> D8/D16 those are the
On Thu, Aug 24, 2017 at 12:29 AM, taii...@gmx.com wrote:
> Ah I see thanks for explaining.
>
> I had read all the AGESA boards were going to be removed, besides the asus
> D8/D16 those are the last and best owner controlled x86 boards.
> Is there a current list of boards to be
On Wed, Aug 23, 2017 at 3:10 PM, Jonathan Neuschäfer
wrote:
> On Wed, Aug 23, 2017 at 09:44:30PM +, ron minnich wrote:
> > On Wed, Aug 23, 2017 at 2:31 PM taii...@gmx.com wrote:
> >
> > > Ah I see thanks for explaining.
> > >
> > > I had read all the
Jonathan Neuschäfer wrote:
> > I would like to have a list of all boards ever supported, along
> > with the last coreboot revision where they can be found.
>
> There is such a page in the wiki[2]. It's probably incomplete. It
> doesn't list commits, either.
>
> We could migrate it into git,
On Wed, Aug 23, 2017 at 09:44:30PM +, ron minnich wrote:
> On Wed, Aug 23, 2017 at 2:31 PM taii...@gmx.com wrote:
>
> > Ah I see thanks for explaining.
> >
> > I had read all the AGESA boards were going to be removed, besides the
> > asus D8/D16 those are the last and best
On Wed, Aug 23, 2017 at 2:31 PM taii...@gmx.com wrote:
> Ah I see thanks for explaining.
>
> I had read all the AGESA boards were going to be removed, besides the
> asus D8/D16 those are the last and best owner controlled x86 boards.
> Is there a current list of boards to be
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/23/2017 04:29 PM, taii...@gmx.com wrote:
> Ah I see thanks for explaining.
>
> I had read all the AGESA boards were going to be removed, besides the
> asus D8/D16 those are the last and best owner controlled x86 boards.
> Is there a current
Ah I see thanks for explaining.
I had read all the AGESA boards were going to be removed, besides the
asus D8/D16 those are the last and best owner controlled x86 boards.
Is there a current list of boards to be removed?
--
coreboot mailing list: coreboot@coreboot.org
I am always sad to see boards go away, especially since it means that the
amount of coreboot I still have code in is smaller by the month, but ...
there's a real opportunity cost to keeping old boards in. We've had cases
where a new, useful feature has to be implemented as a config variable
since
On Wed, Aug 23, 2017 at 2:06 PM, Felipe Sanches wrote:
> Is there an index of which was the latest git commit for each removed board
> ?
> That would help anyone interested in working on them in the future. It is
> not strictly necessary, but would certainly make life
Is there an index of which was the latest git commit for each removed board
?
That would help anyone interested in working on them in the future. It is
not strictly necessary, but would certainly make life easier. And it can't
be that hard to update a wiki page (or something equivalent) any time
Hi,
On 23.08.2017 06:00, taii...@gmx.com wrote:
> Just because a board lacks active developers doesn't mean that no one is
> using it.
right, and we won't stop anybody from using them in the future. Please
keep in mind, when a board is removed from the tree that only means that
the people
2017-08-23 6:00 GMT+02:00 taii...@gmx.com :
> Just because a board lacks active developers doesn't mean that no one is
> using it.
> As a layman I simply can't understand as to how all these seemingly
> insignificant improvements such as CBMEM in ramstage make it worth removing
>
Just because a board lacks active developers doesn't mean that no one is
using it.
As a layman I simply can't understand as to how all these seemingly
insignificant improvements such as CBMEM in ramstage make it worth
removing almost every compatible board from the source, including nearly
all
22 matches
Mail list logo