"Cary Jardin" <cary(a)xprime.com> writes:
> I saw your threads on LinuxBIOS and I hope you don't mind me asking a
> I am running into a problem with the E7500 remapping of PCI space above
> system space.
It only remaps memory not pci space.
> Optimally, I would like it to map below for my specific
> application. Unfortunately I am using an AMI bios that I can't just
> crack open and look at.
> >From you experience, can this be done on the E7500?
It does not sound correct:
The docs for this part of the chipset are available at developer.intel.com
After I turn off framebuffer in linuxbios,I still get
60M memory, But in fact, my memory size is 64M.
How to get another 4M memory?
currently , i use a k7sem mainboard. it work's fine with linuxbios.
I replace the the BIOS with the linuxbios+etherboot. now i want to
use the Xwindows. i want a embedded movie player, since mplayer use
the fbdev output, and can't play it full screen. (sometimes play VCD)
so i want to use the Xwindows to play the movie.
my host system is Debian unstable. i works fine when i use a normal
BIOS. i have strip the system, and get a 14M base system . i test it
under the normal BIOS , i works fine. But when i turn it into linuxbios,
and start the Xwindows. i get a blank screen. :(
what can I do next? can you give me some tips?
I need to build a bios for the clearwater with no fallback/normal images.
Just a single image.
I find myself unsure how to do this, I've not looked in depth at the
fallback/normal build stuff.
Is there a simple option so I can build an image w/o the fallback/normal
stuff on systems like clearwater that are configured for fallback/normal?
I have a dumb question about DoC with LinuxBIOS.
Today, I have requested to port LinuxBIOS on EPIA-M board equipped with DoC
Though I have ported LinuxBIOS to several boards, I have no knowledge and
experience regarding DoC.
The board have seperated 2Mbit flash for BIOS and 32MByte DoC connected to
ISA bus. Therefore I want to put LinuxBIOS on the normal flash part and put
linux on the DoC.
My question is 'What should I do to do this?'.
After reading some documents from M-sys and this mailling list about DoC,
I'm a little confused.
M-sys claim it is compatible with normal HDD and recognized as disk drive
without any software.
Then what is the problem when it comes with LinuxBIOS? If my understanding
is correct, it has built in
software driver which must be executed from the normal BIOS environment. Is
Then again, what should I do to fetch kernel from DoC. should I use ALDO or
Do I need something
like BDK from M-Sys?
Any comment, help will be very thankful.
Embedded S/W Team at ETRI
is possible to find flashroms with at least 6 o 8 Mbits of Memory to
substitute the normal flashrom ..?, i prefer don't use DoC ...
if it's possible, why you use DoC ? by price, by the possibiliti of Disk ?
These days i was asking for many things about LinuxBios ..., this is
because i'm studing the possibility to make my final thesis over
LinuxBios ..., my objective is enlarge the capacities of kernel that is
running into flashrom, just like manage hardware directly, and other
things ..., for this reason i need more space in flashrom ..., and
understand rombios functionality ..., at the moment i only knew about
Linux Kernel ...