linuxconsole-dev

Compiling 2.4.0 with ruby.

[Adam H. <sv...@ea...>]

I get these errors when compiling 2=2E4=2E0 with ruby=2E

vt_ioctl=2Ec: In function `con_set_cmap':
vt_ioctl=2Ec:588: structure has no member named `vcs'
vt_ioctl=2Ec: In function `vt_ioctl':
vt_ioctl=2Ec:933: structure has no member named `vcs'
vt_ioctl=2Ec:945: structure has no member named `vcs'
vt_ioctl=2Ec:1071: structure has no member named `vcs'
vt_ioctl=2Ec:1097: structure has no member named `vcs'
vt_ioctl=2Ec:1143: structure has no member named `vcs'

I'm sure I don't understand what I'm doing and have some kernel config
to do=2E Can I have a go on multiple consoles with cirrus logic (gd5480)
hardware?
What are my limitations and what can I do? Am I limited to some certain
hardware=2E I have a hunch that multiple X sessions are a bit pre-mature
at the moment, but that's what I'm after in the long run=2E

Cheers,
--=20
Adam Huuva / Easter-eggs                 Sp=E9cialiste GNU/Linux
44-46 rue de l'Ouest  -  75014 Paris  -  France -  M=E9tro Gait=E9
Phone: +33 (0) 1 43 35 00 37    -   Fax: +33 (0) 1 41 35 00 76
mailto:sventon@easter-eggs=2Ecom  -   http://www=2Eeaster-eggs=2Ecom

Re: Compiling 2.4.0 with ruby.

[James S. <jsi...@su...>]

> vt_ioctl.c:588: structure has no member named `vcs'

Try the lastest CVS. It is fixed. 

> I'm sure I don't understand what I'm doing and have some kernel config
> to do. 

You can send mne your .config file.

> Can I have a go on multiple consoles with cirrus logic (gd5480)
> hardware?

Not yet. This requires rewriting the fbcon layer which I'm about to do. 

> What are my limitations and what can I do? Am I limited to some certain
> hardware. 

Right now I have only worked with the vgacon and mdacon driver. I got both
working pretty well together.

> I have a hunch that multiple X sessions are a bit pre-mature
> at the moment, but that's what I'm after in the long run.

It can be done with XFree86. You have to do a 

start -vt 0
start -vt 16

This tells it which vc to run on. For the ruby tree 16 VCs belong to one
VT. Unfortunely I haven't got the fbcon layer going yet. Also for each
fbdev driver we have to make them firmware independent as well. Since most
video cards depend on the BIOS to intialize them. Unfortunely PC BIOS
don't see multiple video cards so only the first one on the PCI bus gets
intialized :-(

Re: Compiling 2.4.0 with ruby.

[Adam H. <sv...@ea...>]

James Simmons wrote:
> 
> Try the lastest CVS. It is fixed.
OK. It is. Now I have this instead:

gcc -D__KERNEL__ -I/SDA3/usr/src/linux_patched/include -Wall
-Wstrict-prototypes -O2 -fomit-frame
-pointer -fno-strict-aliasing -pipe -mpreferred-stack-boundary=2
-march=i686    -c -o dummycon.o 
dummycon.c
In file included from
/SDA3/usr/src/linux_patched/include/linux/irq.h:57,
                 from
/SDA3/usr/src/linux_patched/include/asm/hardirq.h:6,
                 from
/SDA3/usr/src/linux_patched/include/linux/interrupt.h:45,
                 from
/SDA3/usr/src/linux_patched/include/linux/kbd_kern.h:4,
                 from
/SDA3/usr/src/linux_patched/include/linux/vt_kern.h:12,
                 from dummycon.c:11:
/SDA3/usr/src/linux_patched/include/asm/hw_irq.h: In function
`x86_do_profile':
/SDA3/usr/src/linux_patched/include/asm/hw_irq.h:198: `current'
undeclared (first use in this fun
ction)
/SDA3/usr/src/linux_patched/include/asm/hw_irq.h:198: (Each undeclared
identifier is reported onl
y once
/SDA3/usr/src/linux_patched/include/asm/hw_irq.h:198: for each function
it appears in.)
In file included from
/SDA3/usr/src/linux_patched/include/linux/kbd_kern.h:4,
                 from
/SDA3/usr/src/linux_patched/include/linux/vt_kern.h:12,
                 from dummycon.c:11:
/SDA3/usr/src/linux_patched/include/linux/interrupt.h: In function
`raise_softirq':
/SDA3/usr/src/linux_patched/include/linux/interrupt.h:89: `current'
undeclared (first use in this
 function)
/SDA3/usr/src/linux_patched/include/linux/interrupt.h: In function
`tasklet_schedule':
/SDA3/usr/src/linux_patched/include/linux/interrupt.h:160: `current'
undeclared (first use in thi
s function)
/SDA3/usr/src/linux_patched/include/linux/interrupt.h: In function
`tasklet_hi_schedule':
/SDA3/usr/src/linux_patched/include/linux/interrupt.h:174: `current'
undeclared (first use in thi
s function)
dummycon.c: At top level:
dummycon.c:64: unknown field `con_switch' specified in initializer
dummycon.c:65: duplicate initializer
dummycon.c:65: (near initialization for `dummy_con.con_blank')
dummycon.c:69: unknown field `con_scrolldelta' specified in initializer
dummycon.c:69: duplicate initializer
dummycon.c:69: (near initialization for `dummy_con.con_scroll')
make[4]: *** [dummycon.o] Error 1
make[4]: Leaving directory `/SDA3/usr/src/linux_patched/drivers/video'
make[3]: *** [first_rule] Error 2
make[3]: Leaving directory `/SDA3/usr/src/linux_patched/drivers/video'
make[2]: *** [_subdir_video] Error 2
make[2]: Leaving directory `/SDA3/usr/src/linux_patched/drivers'
make[1]: *** [_dir_drivers] Error 2
make[1]: Leaving directory `/SDA3/usr/src/linux_patched'
make: *** [stamp-build] Error 2


> You can send mne your .config file.
> 
OK. Thanks. It is attached.

> > Can I have a go on multiple consoles with cirrus logic (gd5480)
> > hardware?
> 
> Not yet. This requires rewriting the fbcon layer which I'm about to do.

So I can't run several vgacons on different graphics cards/chips yet
either?
Due to the bios restriction?

> > I have a hunch that multiple X sessions are a bit pre-mature
> > at the moment, but that's what I'm after in the long run.
> 
> It can be done with XFree86. You have to do a
> 
> start -vt 0
> start -vt 16
> 
> This tells it which vc to run on. For the ruby tree 16 VCs belong to one
> VT. Unfortunely I haven't got the fbcon layer going yet. Also for each
> fbdev driver we have to make them firmware independent as well. Since most
> video cards depend on the BIOS to intialize them. Unfortunely PC BIOS
> don't see multiple video cards so only the first one on the PCI bus gets
> intialized :-(

So not yet. But would the bios still initialize all heads on a multihead
card? No, I guess not, just the first. A job for linuxbios? :)

Cheers,
-- 
Adam Huuva / Easter-eggs                 Spécialiste GNU/Linux
44-46 rue de l'Ouest  -  75014 Paris  -  France -  Métro Gaité
Phone: +33 (0) 1 43 35 00 37    -   Fax: +33 (0) 1 41 35 00 76
mailto:sv...@ea...  -   http://www.easter-eggs.com

Re: Compiling 2.4.0 with ruby.

[James S. <jsi...@su...>]

> > Try the lastest CVS. It is fixed.
> OK. It is. Now I have this instead:
> 
> In file included from
> /SDA3/usr/src/linux_patched/include/linux/irq.h:57,

This is a problem with the standard kernel which our tree is against ;-(

> dummycon.c: At top level:
> dummycon.c:64: unknown field `con_switch' specified in initializer
> dummycon.c:65: duplicate initializer
> dummycon.c:65: (near initialization for `dummy_con.con_blank')
> dummycon.c:69: unknown field `con_scrolldelta' specified in initializer
> dummycon.c:69: duplicate initializer
> dummycon.c:69: (near initialization for `dummy_con.con_scroll')
> make[4]: *** [dummycon.o] Error 1

Fixed and commited.

> > Not yet. This requires rewriting the fbcon layer which I'm about to do.
> 
> So I can't run several vgacons on different graphics cards/chips yet
> either?

Well with vga ISA hardware it is much more difficult to do. Some cards
allowed for you to change the register space but very few allow you to
change the memory region that vga uses (a000). 

> Due to the bios restriction?

Most video cards depend on some code in their firmware to initialize their
hardware to run. This is why if you can't buy say a Voodoo video card for
the mac and plug it into a PC. Vice verse is also true. What is needed is
to figure out which registers the video card needs programmed that the
firware does. This would then allow the driver to be truly platform
independent. On PCs the BIOS is needed to intialize the video
card. Unfortunely they don't initialize more than one.

> > don't see multiple video cards so only the first one on the PCI bus gets
> > intialized :-(
> 
> So not yet. But would the bios still initialize all heads on a multihead
> card? No, I guess not, just the first. A job for linuxbios? :)

If you mean by multihead card a single video card that supports more than
one monitor than no. That would be up to the driver to program both heads.
You still need to initialze the card with the BIOS if you don't know what
regitser specs are needed to initialize the video card. A good example is
the matrox framebuffer driver for this which BTW is BIOS independent :-)