* David Kuehling (dvdkh...@gmx.de) [111029 22:46]:
> BTW it looks like it is impossible to override machtype= parameter from
> the kernel command line configured in boot/grub/grub.cfg, since linux
> code in loongson/common/machtype.c uses the first occurence of
> "machtype=" in arcs_cmdline[]. Is t
* Vladimir 'φ-coder/phcoder' Serbinenko (phco...@gmail.com) [111029 12:55]:
> On 29.10.2011 12:45, Andreas Barth wrote:
> > I personally don't see how we could correctly
> > find out the different variants the linux kernel detects without using
> > the informati
* David Kuehling (dvdkh...@gmx.de) [111029 13:43]:
> I didn't find a method to make linux report the actual mach type that it
> is running with, so I don't know what it fell back to, and I just went
> the safe route of patching my version of grub.
It's displayed as part of /proc/cpuinfo.
Andi
_
* Vladimir 'φ-coder/phcoder' Serbinenko (phco...@gmail.com) [111029 12:42]:
> On 29.10.2011 12:37, Andreas Barth wrote:
> > * David Kuehling (dvdkh...@gmx.de) [111029 11:37]:
> >> according to my /proc/cmdline grub passes
> >> machtype=lemote-fuloong-2f-u
* David Kuehling (dvdkh...@gmx.de) [111029 11:37]:
> according to my /proc/cmdline grub passes
> machtype=lemote-fuloong-2f-unknown as first argument to the linux
> kernel.
Did you see any issues because of that in Linux? Fallback within linux
is MACH_LEMOTE_FL2F which is the one used with the arg
* Vladimir 'φ-coder/phcoder' Serbinenko (phco...@gmail.com) [110812 15:15]:
> On 03.08.2011 13:21, Robert Millan wrote:
> > 2011/7/26 Colin Watson :
> >>> Looks like memory allocations are wrong. Try hardcoding heap at e.g.
> >>> 8100-8200
> >> Sorry, I've not had to mess with this before.
* Robert Millan (r...@gnu.org) [110811 19:10]:
> 2011/7/26 Colin Watson :
> >> Looks like memory allocations are wrong. Try hardcoding heap at e.g.
> >> 8100-8200
> >
> > Sorry, I've not had to mess with this before. Can you point me to what
> > I'd need to change to hardcode a specific he
