Menu
▾
▴
linuxconsole-dev
|
From: Romain D. <do...@ir...> - 2001-08-02 13:04:54
|
Hello, The current (2.4.7) ruby won't compile on my Debian/PPC setup. Here's the error log: ##### gcc -D__KERNEL__ -I/usr/src/linux-2.4.7-ruby/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer -fno-strict-aliasing -fno-common -D__powerpc__ -fsigned-char -msoft-float -pipe -ffixed-r2 -Wno-uninitialized -mmultiple -mstring -c -o offb.o offb.c offb.c:83: warning: initialization from incompatible pointer type offb.c: In function `offb_init_fb': offb.c:303: structure has no member named `cmap_adr' offb.c:377: warning: passing arg 1 of `register_framebuffer' from incompatible pointer type offb.c:240: warning: unused variable `i' offb.c: In function `offb_blank': offb.c:419: `par' undeclared (first use in this function) offb.c:419: (Each undeclared identifier is reported only once offb.c:419: for each function it appears in.) offb.c:427: warning: unreachable code at beginning of switch statement offb.c:453: incompatible type for argument 1 of `fb_set_cmap' offb.c: In function `offb_setcolreg': offb.c:509: warning: dereferencing `void *' pointer offb.c:509: invalid use of void expression offb.c:514: warning: dereferencing `void *' pointer offb.c:514: invalid use of void expression ##### I can post .config if it's needed. I'm going to need a screen (either offb or controlfb) before I can properly port pm3fb (my old ELC is too slow for serious programming :-) TIA -- DOLBEAU Romain | l'histoire est entierement vraie, puisque ENS Cachan / Ker Lann | je l'ai imaginee d'un bout a l'autre do...@ir... | -- Boris Vian |
|
From: James S. <jsi...@tr...> - 2001-08-02 20:41:31
|
> The current (2.4.7) ruby won't compile on my Debian/PPC setup. I fixed those problems. It will compile but I can't test it to see if it works. |
|
From: Romain D. <do...@ir...> - 2001-08-03 07:29:27
|
James Simmons wrote: > I fixed those problems. It will compile but I can't test it to see if it > works. OK thanks a lot I'll try that and report. BTW, would it be possible to become a linuxconsole develloper so that the ruby-fied pm3fb would live on sourceforge ? TIA -- DOLBEAU Romain | l'histoire est entierement vraie, puisque ENS Cachan / Ker Lann | je l'ai imaginee d'un bout a l'autre do...@ir... | -- Boris Vian |
|
From: James S. <jsi...@tr...> - 2001-08-03 16:06:40
|
> OK thanks a lot I'll try that and report. > > BTW, would it be possible to become a linuxconsole develloper > so that the ruby-fied pm3fb would live on sourceforge ? Yes. Just send me your sourceforge account name. |
|
From: <dol...@cl...> - 2001-08-03 17:35:04
|
> Yes. Just send me your sourceforge account name. It's "dolbeau", thanks a lot. No need for emergency, I'll be on vacation starting the 4 of august :-) BTW, neither a offb-only or offb+pm3fb [alpha ruby] or pm3fb-only 2.4.7-ruby will boot on my box, all drop me quickly to xmon. I still have the display on my main monitor [driven by the pm3] working in both case, so it's likely it crashes very early. According to my limited understanding of xmon and System.map, the crashes happen somewhere in register_console (at least the PC seems to point somewhere in register_console...) Don't have the time to investigate the problem right now :-( -- DOLBEAU Romain | We'll know for the first time ENS Cachan / Ker Lann | If we're evil or divine Thesard IRISA / CAPS | -- Dio dol...@cl... | in 'The Last In Line' |
|
From: James S. <jsi...@tr...> - 2001-08-03 17:45:55
|
> It's "dolbeau", thanks a lot. No need for emergency, I'll be on vacation > starting the 4 of august :-) Done. Have a relaxing vaction. When you get back talk to Frank Sirl. He is doing PPC work as well (more input side). > BTW, neither a offb-only or offb+pm3fb [alpha ruby] or pm3fb-only > 2.4.7-ruby will boot on my box, all drop me quickly to xmon. I still > have the display on my main monitor [driven by the pm3] working in both > case, so it's likely it crashes very early. According to my limited > understanding of xmon and System.map, the crashes happen somewhere in > register_console (at least the PC seems to point somewhere in > register_console...) Could you post a ksyoomps or Oops so I can try to track it. |
|
From: Romain D. <do...@ir...> - 2001-08-21 11:41:30
|
James Simmons wrote: > Done. OK. I have a preliminary (i.e. it compiles but is untested) pm3fb for ruby. the only change to mainstream ruby are in include/linux/fb.h (FB_ACCEL_3DLABS_PERMEDIA3 37) drivers/video/Makefile drivers/video/Config.in drivers/video/fbmem.c May I commit the changes to those files ? TIA -- DOLBEAU Romain | l'histoire est entierement vraie, puisque ENS Cachan / Ker Lann | je l'ai imaginee d'un bout a l'autre do...@ir... | -- Boris Vian |
|
From: James S. <jsi...@tr...> - 2001-08-21 20:54:05
|
> OK. I have a preliminary (i.e. it compiles but is untested) pm3fb > for ruby. the only change to mainstream ruby are in > > include/linux/fb.h (FB_ACCEL_3DLABS_PERMEDIA3 37) > drivers/video/Makefile > drivers/video/Config.in > drivers/video/fbmem.c > > May I commit the changes to those files ? Please do :-) k |
|
From: Romain D. <do...@ir...> - 2001-08-22 11:10:23
|
James Simmons wrote: > Please do :-) Done. untested as Ruby won't work on my PPC box. If a x86 user could try... (Sven ? :-) -- DOLBEAU Romain | l'histoire est entierement vraie, puisque ENS Cachan / Ker Lann | je l'ai imaginee d'un bout a l'autre do...@ir... | -- Boris Vian |
|
From: Sven <lu...@dp...> - 2001-08-24 07:42:14
|
On Wed, Aug 22, 2001 at 01:10:17PM +0200, Romain Dolbeau wrote: > James Simmons wrote: > > > Please do :-) > > Done. untested as Ruby won't work on my PPC box. > If a x86 user could try... (Sven ? :-) Sorry for the delay, ... i would gladly try it, but as i don't seem to have the anterior mails, what should i do, and where should i get the ruby tree from ? Friendly, sven Luther |
|
From: Romain D. <do...@ir...> - 2001-08-24 08:03:37
|
Sven wrote: > i would gladly try it, but as i don't seem to have the anterior mails, what > should i do, and where should i get the ruby tree from ? <http://sourceforge.net/projects/linuxconsole/> the rubyfied pm3fb is now integrated :-) note: it compiles, but was never tested. HW accel is disabled (i.e. the functions are there but not used, pm3fb_ops still use cfb_*) TIA for the test, -- DOLBEAU Romain | l'histoire est entierement vraie, puisque ENS Cachan / Ker Lann | je l'ai imaginee d'un bout a l'autre do...@ir... | -- Boris Vian |
|
From: Sven <lu...@dp...> - 2001-08-24 08:37:17
|
On Fri, Aug 24, 2001 at 10:03:28AM +0200, Romain Dolbeau wrote: > Sven wrote: > > > i would gladly try it, but as i don't seem to have the anterior mails, what > > should i do, and where should i get the ruby tree from ? > > <http://sourceforge.net/projects/linuxconsole/> > > the rubyfied pm3fb is now integrated :-) > > note: it compiles, but was never tested. HW accel > is disabled (i.e. the functions are there but not > used, pm3fb_ops still use cfb_*) > > TIA for the test, Ok, will test it as time permitts (possibly notuntil monday evening, but i will try.) That said, i suppose the interresting part of the sourceforge project is the cvs server, as noting else seems to be active. Which cvs module should i get, and it is a whole linux kernel tree or only the console subsystem ? mmm, it seems it is the whole kernel tree, and there is an AGAINST-2.4.7 diff available. Is the stuff i need to test in this patch ? i don't think so since it is 3 weeks old already. Friendly, Sven Luther |
|
From: Romain D. <do...@ir...> - 2001-08-24 08:40:41
|
Sven wrote: > That said, i suppose the interresting part of the sourceforge project is the > cvs server, as noting else seems to be active. Which cvs module should i get, > and it is a whole linux kernel tree or only the console subsystem ? > > mmm, it seems it is the whole kernel tree, and there is an AGAINST-2.4.7 > diff available. Is the stuff i need to test in this patch ? i don't think so > since it is 3 weeks old already. the relevant module is 'ruby', which include a _partial_ kernel tree. you need a regular 2.4.7 and move/copy the ruby files. The AGAINST file is only a label to know the proper kernel version, it's an empty file... -- DOLBEAU Romain | l'histoire est entierement vraie, puisque ENS Cachan / Ker Lann | je l'ai imaginee d'un bout a l'autre do...@ir... | -- Boris Vian |
|
From: Sven <lu...@dp...> - 2001-08-24 08:42:25
|
On Fri, Aug 24, 2001 at 10:40:33AM +0200, Romain Dolbeau wrote: > Sven wrote: > > That said, i suppose the interresting part of the sourceforge project is the > > cvs server, as noting else seems to be active. Which cvs module should i get, > > and it is a whole linux kernel tree or only the console subsystem ? > > > > mmm, it seems it is the whole kernel tree, and there is an AGAINST-2.4.7 > > diff available. Is the stuff i need to test in this patch ? i don't think so > > since it is 3 weeks old already. > > the relevant module is 'ruby', which include a _partial_ kernel > tree. you need a regular 2.4.7 and move/copy the ruby files. > The AGAINST file is only a label to know the proper kernel > version, it's an empty file... Ok, will download it this afternoon, and try it out, don't know if i will have time for it though until next week. Friendly, Sven Luther |
|
From: Sven <lu...@dp...> - 2001-08-25 12:23:19
|
On Fri, Aug 24, 2001 at 10:40:33AM +0200, Romain Dolbeau wrote: > Sven wrote: > > That said, i suppose the interresting part of the sourceforge project is the > > cvs server, as noting else seems to be active. Which cvs module should i get, > > and it is a whole linux kernel tree or only the console subsystem ? > > > > mmm, it seems it is the whole kernel tree, and there is an AGAINST-2.4.7 > > diff available. Is the stuff i need to test in this patch ? i don't think so > > since it is 3 weeks old already. > > the relevant module is 'ruby', which include a _partial_ kernel > tree. you need a regular 2.4.7 and move/copy the ruby files. > The AGAINST file is only a label to know the proper kernel > version, it's an empty file... No, no luck, ... it dies with : unable to handle NULL pointer dereference at virtual address 0000000c eip is c01e60a1 (__fb_try_mode is c01e6020, next is fb_set_var at c01e60d0). call trace seems to be : pm3fb_mode_setup pm3fb_real_setup init kernel_thread (not sure about this one, i missed one digit and had to guess it.) I start the kernel with grub and : title linux (2.4.7-ruby pm3fb) root (hd0,0) kernel (hd0,0)/boot/vmlinuz-2.4.7-ruby root=/dev/hda1 video=pm3fb:mode:0:800x600-75,mode:1:640x400-60,off Hope this is helpfull and i did not mess up some stuff. Note, i got ruby from cvs yesterday, and simply copied the linux directory over to a fresh 2.4.7 tree.? Friendly, Sven Luther |
|
From: James S. <jsi...@tr...> - 2001-08-26 16:23:51
|
> No, no luck, ...
>
> it dies with :
>
> unable to handle NULL pointer dereference at virtual address 0000000c
>
> eip is c01e60a1 (__fb_try_mode is c01e6020, next is fb_set_var at c01e60d0).
>
> call trace seems to be :
>
> pm3fb_mode_setup
>
> pm3fb_real_setup
>
> init
>
> kernel_thread (not sure about this one, i missed one digit and had to guess
> it.)
>
> I start the kernel with grub and :
>
> title linux (2.4.7-ruby pm3fb)
> root (hd0,0)
> kernel (hd0,0)/boot/vmlinuz-2.4.7-ruby root=/dev/hda1
> video=pm3fb:mode:0:800x600-75,mode:1:640x400-60,off
>
> Hope this is helpfull and i did not mess up some stuff.
>
> Note, i got ruby from cvs yesterday, and simply copied the linux directory
> over to a fresh 2.4.7 tree.?
Hm, strange. Lets see. I see what is causing alot of the problems. In the
new fbdev api you have to do the reverse of how you defined your data.
You have:
struct pm3fb_info {
struct fb_info gen;
unsigned long board_num; /* internal board number */
unsigned long use_current;
struct pm3fb_par *current_par;
struct pci_dev *dev; /* PCI device */
unsigned long board_type; /* index in the cardbase */
unsigned char *fb_base; /* framebuffer memory base */
u32 fb_size; /* framebuffer memory size */
unsigned char *p_fb; /* physical address of frame buffer */
unsigned char *v_fb; /* virtual add
...
The upper fbcon layers only can deal with struct fb_info itself. This is
one of the big reasons why the fbcon layer shrunk so much in size for
ruby. You can blindly pass around hardware data without ever touching it
in the upper layers. What you need is:
struct fb_info pm3fb_info.
struct pm3_par {
....
/* Anything hardware specific and we can't shove into struct
* fb_info */
....
}
xxxfb_init()
{
/* fill in par values */
par->fjfjfjf = hjfhfhf;
....
pm2fb_info.par = par;
}
Will this driver work on a pm2 card? I recently came into possesion of
one.
|
|
From: Romain D. <do...@ir...> - 2001-08-27 08:13:38
|
James Simmons wrote: > Hm, strange. Lets see. I see what is causing alot of the problems. In the > new fbdev api you have to do the reverse of how you defined your data. > > The upper fbcon layers only can deal with struct fb_info itself. This is > one of the big reasons why the fbcon layer shrunk so much in size for > ruby. You can blindly pass around hardware data without ever touching it > in the upper layers. What you need is: Well, it was a quick-and-dirty port, I need to fix it, I know :-( I'll try ASAP... thanks for the explanation. More docs is always good :-) > Will this driver work on a pm2 card? I recently came into possesion of > one. No. The chip are similar but not close enough. There's a nold, orhpaned pm2fb but I don't know if it works. Sven tried to talk me into taking over pm2fb maintenance and creating a 'glinfb' or 'pmXfb' for both chipset, but without doc and hardware there's not much I can do... I couldn't even find a card to borrow, it seems pm2 aren't common in France (and the people who sold them on french auction sites have very strange idea about their value) > Do you have serial console going to record any oops? I really like to make > it work on the PPC. I have a SPARCstation ELC just for that :-) But I didn't find time yet :-( -- DOLBEAU Romain | l'histoire est entierement vraie, puisque ENS Cachan / Ker Lann | je l'ai imaginee d'un bout a l'autre do...@ir... | -- Boris Vian |
|
From: James S. <jsi...@tr...> - 2001-08-27 16:48:55
|
> Well, it was a quick-and-dirty port, I need to fix it, I know :-( > I'll try ASAP... thanks for the explanation. More docs is always > good :-) Thanks. I really need to write a white paper soon for 2.5.X. > pm2fb but I don't know if it works. Sven tried to talk me into > taking over pm2fb maintenance and creating a 'glinfb' or 'pmXfb' for > both chipset, but without doc and hardware there's not much I can do... > I couldn't even find a card to borrow, it seems pm2 aren't common > in France (and the people who sold them on french auction sites have > very strange idea about their value) I have the card and the docs for it. I can give it a try. > > Do you have serial console going to record any oops? I really like to make > > it work on the PPC. > > I have a SPARCstation ELC just for that :-) But I didn't find time > yet :-( I just need detail info from ksymoops and what you did to cause the problem. |
|
From: <dol...@cl...> - 2001-08-27 16:59:39
|
> I just need detail info from ksymoops and what you did to cause the > problem.=20 Well, I do nothing and I get nothing :-) Seriously, without xmon, I get no message. After the BootX messages (arch:exit) I usually get the console (framebuffer or serial) to start displaying boot messages, but with 2.4.7-ruby I get nothing. The computer stand still, doing nothing (the power supply fan audibly slow down after a short while...). Serial console works fine with other 2.4.x, but I may have forgotten a kernel option in ruby... I'll check into that and also try with xmon enabled. --=20 Romain DOLBEAU | Ce que l'on con=E7oit bien s'=E9nonce ENS Cachan / Ker Lann | clairement, et les mots pour le dire Thesard IRISA / CAPS | arrivent ais=E9ment. dol...@cl... | -- Nicolas Boileau |
|
From: James S. <jsi...@tr...> - 2001-09-03 02:32:53
|
> Seriously, without xmon, I get no message. After the BootX messages > (arch:exit) I usually get the console (framebuffer or serial) to start > displaying boot messages, but with 2.4.7-ruby I get nothing. The > computer stand still, doing nothing (the power supply fan audibly slow > down after a short while...). Serial console works fine with other > 2.4.x, but I may have forgotten a kernel option in ruby... I'll check > into that and also try with xmon enabled. Can you send me your .config file? I like to see your setting. The only thing that could have caused this problem is the console lock but I have made that transparent to the console drivers now :-) It could have been a problem with bust spinlock. I did a bunch of changes just a little bit ago which I commited. Give the new code a try. |
|
From: Romain D. <do...@ir...> - 2001-09-04 08:44:14
|
James Simmons wrote: > > I did a bunch of changes just a little > bit ago which I commited. Give the new code a try. #### drivers/input/inputdrv.o: In function `usb_make_path': drivers/input/inputdrv.o(.text+0x44c0): undefined reference to `snprintf' #### I don't thnk I changed anything in .config, and it used to compile... the offending snprintf come from driver/input/hid_core.c, it seems. -- DOLBEAU Romain | l'histoire est entierement vraie, puisque ENS Cachan / Ker Lann | je l'ai imaginee d'un bout a l'autre do...@ir... | -- Boris Vian |
|
From: James S. <jsi...@tr...> - 2001-09-04 16:57:56
|
> #### > drivers/input/inputdrv.o: In function `usb_make_path': > drivers/input/inputdrv.o(.text+0x44c0): undefined reference to > `snprintf' > #### > > I don't thnk I changed anything in .config, and it used to compile... > > the offending snprintf come from driver/input/hid_core.c, it > seems. It didn't compile. It gave me a warning but went on its way. I did notice this. It appears the kernel lacks a snprintf function. This might explain your crashes. It loks like it will have to be replaced by sprintf. |
|
From: Vojtech P. <vo...@su...> - 2001-09-04 17:43:42
|
On Tue, Sep 04, 2001 at 09:57:38AM -0700, James Simmons wrote: > > > #### > > drivers/input/inputdrv.o: In function `usb_make_path': > > drivers/input/inputdrv.o(.text+0x44c0): undefined reference to > > `snprintf' > > #### > > > > I don't thnk I changed anything in .config, and it used to compile... > > > > the offending snprintf come from driver/input/hid_core.c, it > > seems. > > It didn't compile. It gave me a warning but went on its way. I did notice > this. It appears the kernel lacks a snprintf function. This might explain > your crashes. It loks like it will have to be replaced by sprintf. Odd. include/linux/kernel.h:65:extern int snprintf(char * buf, size_t size, const char * fmt, ...); Oops, maybe I used an -ac kernel ... -- Vojtech Pavlik SuSE Labs |
|
From: James S. <jsi...@tr...> - 2001-09-04 18:23:04
|
> Odd. > > include/linux/kernel.h:65:extern int snprintf(char * buf, size_t size, const char * fmt, ...); Yeap. It is not present in the standard tree. |
|
From: Vojtech P. <vo...@su...> - 2001-09-04 22:20:28
|
On Tue, Sep 04, 2001 at 11:22:56AM -0700, James Simmons wrote: > > Odd. > > > > include/linux/kernel.h:65:extern int snprintf(char * buf, size_t size, const char * fmt, ...); > > Yeap. It is not present in the standard tree. Could we possibly add it to our tree? It makes much easier to avoid buffer overruns, which are rather a big problem when they're in the kernel. -- Vojtech Pavlik SuSE Labs |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X