Video Card to Lite5200

Video Card to Lite5200

[Alan Carvalho]

[-- Attachment #1: Type: text/plain, Size: 1110 bytes --]

Hi Denx,
I am just looking for a cheaper video card to use with Lite5200 board.
CoralP is very expansive, then I will use ATI Rage Mobility.

I see some reference to this board at:
http://ozlabs.org/pipermail/linuxppc-embedded/2004-July/014848.html

Here in Brazil I get an "ATI RAGE XL 8MB PCI" (ATI Mobility 8M TV PCI),
it is PCI v. 2.2 (support 3.3V and 5V).

But I found some tips here at ozlabs:

"Other possible problem is that i found with ATI Rage Mobility M1 EVA board
that it's 723 3.3V regulator needed as default +12V to operate."

Well, my video card is not ATI Rage Mobility M1 EVA, it has not 723
regulator, it use MTD3302 as regulator, do you know if I need change
something on the Lite5200's PCI slot to it work with this video card?

My Lite5200 is Version 2.0, and Freescale connected some wire (small cables)
to PCI slot, maybe to fix some PCI problems.

I am using linux kernel 2.6.14, downloaded from denx's web site. Linux is
running fine in this board, but until now I am using only serial console.
Now I want use a video card with it.

Best regards,

Alan

[-- Attachment #2: Type: text/html, Size: 1434 bytes --]

Re: Video Card to Lite5200

[Wolfgang Denk]

Dear Alan,

in message <dc70db7d0512051130s498f7d5fk42a0f4886c006efd@mail.gmail.com> you wrote:
>
> I am just looking for a cheaper video card to use with Lite5200 board.
> CoralP is very expansive, then I will use ATI Rage Mobility.

Make sure that you don't need to run any (x86) BIOS code on your card
to initialize it. This is the main issue with most graphics cards.

> Well, my video card is not ATI Rage Mobility M1 EVA, it has not 723
> regulator, it use MTD3302 as regulator, do you know if I need change
> something on the Lite5200's PCI slot to it work with this video card?

If your card is a true 3.3V PCI card it should be at  least  possible
to  attach  and  test it. Chances are that it does not work (at least
not without some amount of work).

> My Lite5200 is Version 2.0, and Freescale connected some wire (small cables)
> to PCI slot, maybe to fix some PCI problems.

You probably want to ask FS about this.

> I am using linux kernel 2.6.14, downloaded from denx's web site. Linux is

Note that the 5200 code in the kernel is work in progress. I  do  not
cleaim  that it does work in any way. If you want stable code use our
2.4.25 kernel instead.

> running fine in this board, but until now I am using only serial console.
> Now I want use a video card with it.

Well, if your time is worth anything you  might  find  out  that  the
CoralP  is the cheaper solution - or using a graphics controller that
can be attached directly to the bus.

Best regards,

Wolfgang Denk

-- 
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
In general, they do what you want, unless you want consistency.
                                    - Larry Wall in the perl man page

Re: Video Card to Lite5200

[Alessandro Rubini]

> Note that the 5200 code in the kernel is work in progress. I  do  not
> cleaim  that it does work in any way. If you want stable code use our
> 2.4.25 kernel instead.

FWIW, I have your 2.6.14 happily running on the lite5200, with PCI,
IDE (no DMA though) and flash.

I can publish the patches, if anyone is interested. Until now I didn't,
as Sylvain's work is considered the official one (but it didn't have
IDE last time I checked -- and I don't have bitkeeper to pull it).

/alessandro

Re: Video Card to Lite5200

[roger blofeld]

What is the status of the mpc5200 support? I see Sylvain's repository
is still at 2.6.12 (5 months old).

http://gitbits.246tnt.com/gitweb.cgi?p=linux-2.6-mpc52xx.git;a=summary

The current kernel.org kernel doesn't appear to support fec/DMA. Is
there a plan to get networking support into the mainstream kernel?

Thanks
-rb

--- Alessandro Rubini <rubini@gnudd.com> wrote:

> 
> > Note that the 5200 code in the kernel is work in progress. I  do 
> not
> > cleaim  that it does work in any way. If you want stable code use
> our
> > 2.4.25 kernel instead.
> 
> FWIW, I have your 2.6.14 happily running on the lite5200, with PCI,
> IDE (no DMA though) and flash.
> 
> I can publish the patches, if anyone is interested. Until now I
> didn't,
> as Sylvain's work is considered the official one (but it didn't have
> IDE last time I checked -- and I don't have bitkeeper to pull it).
> 
> /alessandro
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
> 



		
__________________________________________ 
Yahoo! DSL – Something to write home about. 
Just $16.99/mo. or less. 
dsl.yahoo.com 

Re: Video Card to Lite5200

[Alan Carvalho]

[-- Attachment #1: Type: text/plain, Size: 588 bytes --]

Hi Roger,

On 12/7/05, roger blofeld <blofeldus@yahoo.com> wrote:
>
> What is the status of the mpc5200 support? I see Sylvain's repository
> is still at 2.6.12 (5 months old).
>
> http://gitbits.246tnt.com/gitweb.cgi?p=linux-2.6-mpc52xx.git;a=summary
>
> The current kernel.org kernel doesn't appear to support fec/DMA. Is
> there a plan to get networking support into the mainstream kernel?


I am using linux kernel 2.6.14, downloaded from denx site, it is supporting
FEC correctly, well it show a silly error msg, but work fine.


Thanks
> -rb


Cheers,

Alan

[-- Attachment #2: Type: text/html, Size: 1175 bytes --]

Re: Video Card to Lite5200

[Wolfgang Denk]

In message <20051207172321.77464.qmail@web53515.mail.yahoo.com> you wrote:
> 
> The current kernel.org kernel doesn't appear to support fec/DMA. Is
> there a plan to get networking support into the mainstream kernel?

I don;t know - the patches were submitted to this list  a  long  time
ago; we added them to our repository without any additional problems;
see http://www.denx.de/cgi-bin/gitweb.cgi?p=linux-2.6-denx.git

Best regards,

Wolfgang Denk

-- 
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
If ignorance is bliss, why aren't there more happy people?

Re: Video Card to Lite5200

[bennett78]

[-- Attachment #1: Type: text/plain, Size: 2354 bytes --]

Wolfgang Denk wrote:

>Dear Alan,
>
>in message <dc70db7d0512051130s498f7d5fk42a0f4886c006efd@mail.gmail.com> you wrote:
>  
>
>>I am just looking for a cheaper video card to use with Lite5200 board.
>>CoralP is very expansive, then I will use ATI Rage Mobility.
>>    
>>
>
>Make sure that you don't need to run any (x86) BIOS code on your card
>to initialize it. This is the main issue with most graphics cards.
>
>  
>
>>Well, my video card is not ATI Rage Mobility M1 EVA, it has not 723
>>regulator, it use MTD3302 as regulator, do you know if I need change
>>something on the Lite5200's PCI slot to it work with this video card?
>>    
>>
>
>If your card is a true 3.3V PCI card it should be at  least  possible
>to  attach  and  test it. Chances are that it does not work (at least
>not without some amount of work).
>
>  
>
>>My Lite5200 is Version 2.0, and Freescale connected some wire (small cables)
>>to PCI slot, maybe to fix some PCI problems.
>>    
>>
>
>You probably want to ask FS about this.
>
>  
>
>>I am using linux kernel 2.6.14, downloaded from denx's web site. Linux is
>>    
>>
>
>Note that the 5200 code in the kernel is work in progress. I  do  not
>cleaim  that it does work in any way. If you want stable code use our
>2.4.25 kernel instead.
>
>  
>
>>running fine in this board, but until now I am using only serial console.
>>Now I want use a video card with it.
>>    
>>
>
>Well, if your time is worth anything you  might  find  out  that  the
>CoralP  is the cheaper solution - or using a graphics controller that
>can be attached directly to the bus.
>  
>
Wolfgang:
The denx.de web site looks great.

Where can someone get this PCI card?  Do I have to contact Fujitsu 
directly? Cost?
The Fujitsu CoralP evaluation board MB86295EB01? or did you use the 
Coral PA?
I saw a posting that you also had some streaming video running.  Tell me 
more.
What resolution? 4CIF (full DVD)
What display?  LCD SVGA (800x600) and/or VGA analog port?
Software MPEG decoder or does the Coral  have a decoder?
Which player did you use?
Is all this covered in some release notes?
Was the katix stuff ever integrated into linux_2_4_development?
How does Wolfgang make a living if he spends all his time answering our 
questions?

thanks,
Frank Bennett

>Best regards,
>
>Wolfgang Denk
>  
>
*//* <mailto:frank.bennett@triadsyseng.com>


[-- Attachment #2: Type: text/html, Size: 3658 bytes --]

Re: Video Card to Lite5200

[Wolfgang Denk]

In message <439752BE.9030207@digis.net> you wrote:
>
> The denx.de web site looks great.

Thanks :-)

> Where can someone get this PCI card?  Do I have to contact Fujitsu 
> directly? Cost?

I guess you have to contact Fujitsu directly; we worked with  Fujitsu
Microelectronics Europe.

> The Fujitsu CoralP evaluation board MB86295EB01? or did you use the 

Yes.

> Coral PA?

No.

> I saw a posting that you also had some streaming video running.  Tell me 
> more.

See ftp://ftp.denx.de/pub/fujitsu/Coral-P/README.html

> What resolution? 4CIF (full DVD)
> What display?  LCD SVGA (800x600) and/or VGA analog port?

We used a 1024 x 768 LCD.

> Software MPEG decoder or does the Coral  have a decoder?

There was no decoder involved at all. The  CoralP  can  stream  video
directly,  without  any CPU load :-) We used the "zvideo" application
for demos - see above.

> Which player did you use?

None. Just a video source like a standard DVD player or a camera.

> Is all this covered in some release notes?

See the README.html

> Was the katix stuff ever integrated into linux_2_4_development?

Yes, it was. See the drivers/spi/ diretory in our  linuxppc_2_4_devel
tree, or
http://www.denx.de/cgi-bin/gitweb.cgi?p=linuxppc_2_4_devel.git;a=tree;h=464f005880de29947ee7d2d8941446c4ba76b0f8;hb=95300e1ab7d8a330784a882db868e355af6d638a;f=drivers/spi

> How does Wolfgang make a living if he spends all his time answering our 
> questions?

Dunno. Next question, please :-)


Best regards,

Wolfgang Denk

-- 
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
Bradley's Bromide: If computers get too  powerful,  we  can  organize
them into a committee - that will do them in.

Re: Video Card to Lite5200

[Alessandro Rubini]

> What is the status of the mpc5200 support? I see Sylvain's repository
> is still at 2.6.12 (5 months old).

I just published what I've done (on a previous 2.6.14-rc3 tree by Denx).
It's in ftp://gnudd.com/pub/patches/mpc5200/ (also http://).

I used Sylvain's FEC support, hacked a mb() to make PCI initialize
and ported PIO-mode IDE from 2.4 (with a gross hack about port addresses),
enabled some MTD configurations so cmdlineparts work fine.

/alessandro, who doesn't have a 5200 with him any more.

Re: Video Card to Lite5200

[White]

Am Wed, 7 Dec 2005 09:23:21 -0800 (PST) schrieb roger blofeld
<blofeldus@yahoo.com> :

> What is the status of the mpc5200 support? I see Sylvain's repository
> is still at 2.6.12 (5 months old).
> 
> http://gitbits.246tnt.com/gitweb.cgi?p=linux-2.6-mpc52xx.git;a=summary
> 
> The current kernel.org kernel doesn't appear to support fec/DMA. Is
> there a plan to get networking support into the mainstream kernel?
> 
> Thanks
> -rb
> 


i think Sylvians should be update in some days. I hope.
you can pull his rep. without problems on current 2.6.15-rc4.

DMA is a problem, because the implementation from Freescale use binary
data, and has some dirty points. This would never be included in the
mainstream kernel. Sylvian has included the new DMA .. works fine for
FEC.

If someone get this new implementtion running with AC97 or PCI would be
fine.

Re: Video Card to Lite5200

[Wolfgang Denk]

In message <20051208065907.26c2b1d0@White64> you wrote:
>
> DMA is a problem, because the implementation from Freescale use binary
> data, and has some dirty points. This would never be included in the
> mainstream kernel. Sylvian has included the new DMA .. works fine for
> FEC.

...did you try this on Rev. B (like B3) silicon?

What I cannot understand is why there were no attempots to co-operate
on this with Freescale. They offered their help here on the list...

Best regards,

Wolfgang Denk

-- 
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
Brain fried - Core dumped

Re: Video Card to Lite5200

[Andrey Volkov]

Wolfgang Denk wrote:
> In message <20051208065907.26c2b1d0@White64> you wrote:
> 
>>DMA is a problem, because the implementation from Freescale use binary
>>data, and has some dirty points. This would never be included in the
>>mainstream kernel. Sylvian has included the new DMA .. works fine for
>>FEC.
> 
> 
> ...did you try this on Rev. B (like B3) silicon?
> 
> What I cannot understand is why there were no attempots to co-operate
> on this with Freescale. They offered their help here on the list...
> 
Cooperation? With Freescale? THEY don't wish it.

About Bestcomm DMA tasks, fec, PCI ... in kernel.

1) Quotation from Freescale support (AFAIK standard answer to
everybody):
===============================================================
"Dear Andrey Volkov,

In reply to your message regarding Service Request SR 1-214731336 (see
details below):

Freescale doesn't disclose the Bestcomm specifications. Alas, I can't
govern this policy.

The customers can use BestComm API with precompiled BestComm images.

OEM customers can create a custom images from a redy for use tasks.

So, Freescale do not give an opportunity for customers to write their
own BestComm tasks.

Should you need to contact us with regard to this message, please see
the notes below.
Best Regards,
Pavel

---------------------------------------------------------------------
This message is in reply to:Activity ID: 1-3KDNVD
Comment:
Dear Andrey Volkov,

In reply to your message regarding Service Request SR 1-214731336 (see
details below):

As far as i know, Freescale do not provide ability to create BestComm
tasks. OEM customers can only link ready for use tasks into BestComm image.

I've asked the factory about current Freescale policy regarding BestComm
development tools and documentation. I'll send their reply to you ASAP.

Please accept my apology for possible delay.

Should you need to contact us with regard to this message, please see
the notes below.
Best Regards,
Pavel

===============================================================

2) Whithout Bestcomm spec you couldn't write right DMA tasklet
or FIX FREESCALE BestcommAPI images (rev B. and fec as ex.),
and hence eth, pci, ide, or something else, like custom mem mapped
device will not work (in worst case) or will work SLOW.

3) Bestcomm API doesn't freely available (you couldn't download it
from MPC5200 page).

3) I and Sylvain try some reverse engineering work of bestcomm u-code,
docos draft is here: http://patchwork.ozlabs.org/linuxppc/patch?id=2057.
So, I repeat my proposal: if somebody have more info, please, expand
this doco.

--
Regards
Andrey Volkov

P.S. I feel like Freescale wish to kill this fine proc or restrict
OS (linux in particular) that could run on it, for they one known
internal reasons.

MPC5200 RTC

[bennett78]

[-- Attachment #1.1: Type: text/plain, Size: 1147 bytes --]

 *  The /dev/rtc interface will block on reads until an interrupt
 *  has been received. If a RTC interrupt has already happened,
 *  it will output an unsigned long and then block.

Paul Gortmaker's  rtctest (included below) works really well on my x86
machine  (driver/char/rtc.c) as a nice way for a user process to wait on 
ticks
of a programable frequency (via ioctl).

Under Denx linuxppc_2_4_devel MPC5200 I've tried:
    driver/char/rtc.c - kernel panics
       seems to need a RTC_IRQ to be defined
       include/linux/mc14681rtc.h mentions #define RTC_IRQ 8 ?
    CONFIG_PPC_RTC also panics
    driver/char/genrtc.c (with #define CONFIG_GEN_RTC_X)
       sort of works but I get the following:
       gen_rtc_interrupt: system delaying clock ticks?

The internal MPC5200 RTC doesn't seem supported.
I see a lot of references to external RTCs, probably because
the standby power for the 5200 is high. I would like to
use a timer as the RTC interrupt and add an external RTC
later as a time reference (none on Lite5200 dev brd).
How best can I assign a GPTx as an interrupt? other than re-write
genrtc.c?

thanks,
Frank Bennett




*//*


[-- Attachment #1.2: Type: text/html, Size: 1820 bytes --]

[-- Attachment #2: rtctest.c --]
[-- Type: text/x-c, Size: 4562 bytes --]

/*
 *	Real Time Clock Driver Test/Example Program
 *
 *	Compile with:
 *		gcc -s -Wall -Wstrict-prototypes rtctest.c -o rtctest
 *
 *	Copyright (C) 1996, Paul Gortmaker.
 *
 *	Released under the GNU General Public License, version 2,
 *	included herein by reference.
 *
 */
#define spinlock_t int

#include <stdio.h>
#include <linux/mc146818rtc.h>
#include <sys/ioctl.h>
#include <sys/time.h>
#include <sys/types.h>
#include <fcntl.h>
#include <unistd.h>
#include <errno.h>

void main(void) {

int i, fd, retval, irqcount = 0;
unsigned long tmp, data;
struct rtc_time rtc_tm;

fd = open ("/dev/rtc", O_RDONLY);

if (fd ==  -1) {
	perror("/dev/rtc");
	exit(errno);
}

fprintf(stderr, "\n\t\t\tRTC Driver Test Example.\n\n");

/* Turn on update interrupts (one per second) */
retval = ioctl(fd, RTC_UIE_ON, 0);
if (retval == -1) {
	perror("ioctl");
	exit(errno);
}

fprintf(stderr, "Counting 5 update (1/sec) interrupts from reading /dev/rtc:");
fflush(stderr);
for (i=1; i<6; i++) {
	/* This read will block */
	retval = read(fd, &data, sizeof(unsigned long));
	if (retval == -1) {
		perror("read");
		exit(errno);
	}
	fprintf(stderr, " %d",i);
	fflush(stderr);
	irqcount++;
}

fprintf(stderr, "\nAgain, from using select(2) on /dev/rtc:");
fflush(stderr);
for (i=1; i<6; i++) {
	struct timeval tv = {5, 0};	/* 5 second timeout on select */
	fd_set readfds;

	FD_ZERO(&readfds);
	FD_SET(fd, &readfds);
	/* The select will wait until an RTC interrupt happens. */
	retval = select(fd+1, &readfds, NULL, NULL, &tv);
	if (retval == -1) {
		perror("select");
		exit(errno);
	}
	/* This read won't block unlike the select-less case above. */
	retval = read(fd, &data, sizeof(unsigned long));
	if (retval == -1) {
		perror("read");
		exit(errno);
	}
	fprintf(stderr, " %d",i);
	fflush(stderr);
	irqcount++;
}

/* Turn off update interrupts */
retval = ioctl(fd, RTC_UIE_OFF, 0);
if (retval == -1) {
	perror("ioctl");
	exit(errno);
}

/* Read the RTC time/date */
retval = ioctl(fd, RTC_RD_TIME, &rtc_tm);
if (retval == -1) {
	perror("ioctl");
	exit(errno);
}

fprintf(stderr, "\n\nCurrent RTC date/time is %d-%d-%d, %02d:%02d:%02d.\n",
	rtc_tm.tm_mday, rtc_tm.tm_mon + 1, rtc_tm.tm_year + 1900,
	rtc_tm.tm_hour, rtc_tm.tm_min, rtc_tm.tm_sec);

/* Set the alarm to 5 sec in the future, and check for rollover */
rtc_tm.tm_sec += 5;
if (rtc_tm.tm_sec >= 60) {
	rtc_tm.tm_sec %= 60;
	rtc_tm.tm_min++;
}
if  (rtc_tm.tm_min == 60) {
	rtc_tm.tm_min = 0;
	rtc_tm.tm_hour++;
}
if  (rtc_tm.tm_hour == 24)
	rtc_tm.tm_hour = 0;

retval = ioctl(fd, RTC_ALM_SET, &rtc_tm);
if (retval == -1) {
	perror("ioctl");
	exit(errno);
}

/* Read the current alarm settings */
retval = ioctl(fd, RTC_ALM_READ, &rtc_tm);
if (retval == -1) {
	perror("ioctl");
	exit(errno);
}

fprintf(stderr, "Alarm time now set to %02d:%02d:%02d.\n",
	rtc_tm.tm_hour, rtc_tm.tm_min, rtc_tm.tm_sec);

/* Enable alarm interrupts */
retval = ioctl(fd, RTC_AIE_ON, 0);
if (retval == -1) {
	perror("ioctl");
	exit(errno);
}

fprintf(stderr, "Waiting 5 seconds for alarm...");
fflush(stderr);
/* This blocks until the alarm ring causes an interrupt */
retval = read(fd, &data, sizeof(unsigned long));
if (retval == -1) {
	perror("read");
	exit(errno);
}
irqcount++;
fprintf(stderr, " okay. Alarm rang.\n");

/* Disable alarm interrupts */
retval = ioctl(fd, RTC_AIE_OFF, 0);
if (retval == -1) {
	perror("ioctl");
	exit(errno);
}

/* Read periodic IRQ rate */
retval = ioctl(fd, RTC_IRQP_READ, &tmp);
if (retval == -1) {
	perror("ioctl");
	exit(errno);
}
fprintf(stderr, "\nPeriodic IRQ rate was %ldHz.\n", tmp);

fprintf(stderr, "Counting 20 interrupts at:");
fflush(stderr);

/* The frequencies 128Hz, 256Hz, ... 8192Hz are only allowed for root. */
for (tmp=2; tmp<=64; tmp*=2) {

	retval = ioctl(fd, RTC_IRQP_SET, tmp);
	if (retval == -1) {
		perror("ioctl");
		exit(errno);
	}

	fprintf(stderr, "\n%ldHz:\t", tmp);
	fflush(stderr);

	/* Enable periodic interrupts */
	retval = ioctl(fd, RTC_PIE_ON, 0);
	if (retval == -1) {
		perror("ioctl");
		exit(errno);
	}

	for (i=1; i<21; i++) {
		/* This blocks */
		retval = read(fd, &data, sizeof(unsigned long));
		if (retval == -1) {
			perror("read");
			exit(errno);
		}
		fprintf(stderr, " %d",i);
		fflush(stderr);
		irqcount++;
	}

	/* Disable periodic interrupts */
	retval = ioctl(fd, RTC_PIE_OFF, 0);
	if (retval == -1) {
		perror("ioctl");
		exit(errno);
	}
}

fprintf(stderr, "\n\n\t\t\t *** Test complete ***\n");
fprintf(stderr, "\nTyping \"cat /proc/interrupts\" will show %d more events on IRQ 8.\n\n",
								 irqcount);

close(fd);

} /* end main */

Re: Video Card to Lite5200

[Benjamin Herrenschmidt]

On Wed, 2005-12-07 at 20:51 +0100, Wolfgang Denk wrote:
> In message <20051207172321.77464.qmail@web53515.mail.yahoo.com> you wrote:
> > 
> > The current kernel.org kernel doesn't appear to support fec/DMA. Is
> > there a plan to get networking support into the mainstream kernel?
> 
> I don;t know - the patches were submitted to this list  a  long  time
> ago; we added them to our repository without any additional problems;
> see http://www.denx.de/cgi-bin/gitweb.cgi?p=linux-2.6-denx.git

Any reason why you keep that repository instead of submiting the patches
for proper upstream inclusion or to linuxppc-dev at least ?

Ben.

Re: Video Card to Lite5200

[Wolfgang Denk]

In message <1151709367.27137.4.camel@localhost.localdomain> you wrote:
>
> > I don;t know - the patches were submitted to this list  a  long  time
> > ago; we added them to our repository without any additional problems;
> > see http://www.denx.de/cgi-bin/gitweb.cgi?p=linux-2.6-denx.git
> 
> Any reason why you keep that repository instead of submiting the patches
> for proper upstream inclusion or to linuxppc-dev at least ?

We submit patches every now and then, as time permits.  My  intention
is to keep the differences between our tree and kernel.org minimal.

But you know how this goes: just adding support for a new board means
sending patches to the linuxppc_dev, mtd, i2c, usb,  lm_sensors,  ...
mailing  lists. Then you have to wait some time, then you resend. and
you have to keep track of all these things.  And  the  board  support
will  not  work  before the last piece of the puzze has been accepted
and merged and pushed upstream. All this takes a lot  of  effort  and
even  more  calendar time. We need a way to provide a solution to our
customers fast - that's why we maintain our own development branch.

I'd be happy if you could recommend a better approach to handle this.

Best regards,

Wolfgang Denk

-- 
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
The management question ... is not _whether_ to build a pilot  system
and  throw  it away. You _will_ do that. The only question is whether
to plan in advance to build a throwaway, or to promise to deliver the
throwaway to customers.       - Fred Brooks, "The Mythical Man Month"

Re: Video Card to Lite5200

[Benjamin Herrenschmidt]

On Sat, 2006-07-01 at 11:15 +0200, Wolfgang Denk wrote:
> In message <1151709367.27137.4.camel@localhost.localdomain> you wrote:
> >
> > > I don;t know - the patches were submitted to this list  a  long  time
> > > ago; we added them to our repository without any additional problems;
> > > see http://www.denx.de/cgi-bin/gitweb.cgi?p=linux-2.6-denx.git
> > 
> > Any reason why you keep that repository instead of submiting the patches
> > for proper upstream inclusion or to linuxppc-dev at least ?
> 
> We submit patches every now and then, as time permits.  My  intention
> is to keep the differences between our tree and kernel.org minimal.
> 
> But you know how this goes: just adding support for a new board means
> sending patches to the linuxppc_dev, mtd, i2c, usb,  lm_sensors,  ...
> mailing  lists. Then you have to wait some time, then you resend. and
> you have to keep track of all these things.  And  the  board  support
> will  not  work  before the last piece of the puzze has been accepted
> and merged and pushed upstream. All this takes a lot  of  effort  and
> even  more  calendar time. We need a way to provide a solution to our
> customers fast - that's why we maintain our own development branch.
> 
> I'd be happy if you could recommend a better approach to handle this.

Oh, it's fine to maintain a dev. branch, but I haven't seen you submit
stuff to linuxppc-dev for some time so I wanted to make sure you were
still on track :)

Ben.

Re: Video Card to Lite5200

[Wolfgang Denk]

In message <dc70db7d0512080518r674f4025s8e52302e0d3f4249@mail.gmail.com> you wrote:
>
> What you think?
> Is it normal Linux on Lite5200 don't show the PCI card info?

No - at least not if you expect the card to work.

Or maybe it *is* normal - as an indication that  the  card  does  not
work ;-)


Best regards,

Wolfgang Denk

-- 
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
"Just think, with VLSI we can have 100 ENIACS on a chip!"
- Alan Perlis

Re: Video Card to Lite5200

[Alan Carvalho]

[-- Attachment #1: Type: text/plain, Size: 1319 bytes --]

Hi Denx,

I still doing some tests with ATI Video cards, as I said before the card
work fine on my PC.

I compiled the 2.6.14 kernel to Lite5200 with /proc/pci support, then when I
execute:

/ # cat /proc/pci
PCI devices found:
  Bus  0, device  26, function  0:
    Class 0680: PCI device 1057:5803 (rev 0).
      Master Capable.  Latency=248.
      Non-prefetchable 32 bit memory at 0xa0000000 [0xa003ffff].
/ #

It don't list the card placed at PCI slot, on PC using "lspci -v" I see:

0000:00:0c.0 VGA compatible controller: ATI Technologies Inc Rage Mobility
P/M (rev 64) (prog-if 00 [VGA])
        Subsystem: 1002:4c52
        Flags: bus master, stepping, medium devsel, latency 32, IRQ 10
        Memory at ed000000 (32-bit, non-prefetchable) [size=16M]
        I/O ports at d800 [size=256]
        Memory at ec800000 (32-bit, non-prefetchable) [size=4K]
        Expansion ROM at 20000000 [disabled] [size=128K]
        Capabilities: [5c] Power Management version 1

What you think?
Is it normal Linux on Lite5200 don't show the PCI card info?

I am looking for an "ATI Rage XL Xpert98" because Linux kernel has support
to initialize it without BIOS help (CONFIG_FB_ATY_XL_INIT).
I see some post at some list from people using this board on no x86
platform.

Cheers,

Alan

[-- Attachment #2: Type: text/html, Size: 1812 bytes --]