* Re: Wolfgang's updates
[not found] <3A9EEB84.63C6412@mvista.com>
@ 2001-03-12 21:57 ` Wolfgang Denk
0 siblings, 0 replies; 5+ messages in thread
From: Wolfgang Denk @ 2001-03-12 21:57 UTC (permalink / raw)
To: Dan Malek, Tom Rini; +Cc: linuxppc-dev
Hi Dan, Tom,
in message <3A9EEB84.63C6412@mvista.com> you wrote:
>
> I finally got around to pushing some of Wolfgang's patches.
> There were lots of files touched outside of the PowerPC directories,
> that I simply can't update (like the flash and IDE stuff). I
Thank you very much. That's a really big improvemnt for us.
Ummm... The flash stuff is just adding NEW files. The fact they have
been tested on PPC only should not create a problem adding the files.
Many people add x86 drivers that don't work on PPC ;-)
Anyway.
I'm back in sync with the 2.4 tree (2.4.3-pre3); new patches plus
README files with some short explanations are can be found in
ftp://ftp.denx.de/pub/LinuxPPC/usr/src/patches/
In case you have problems with the patches, there is a tarball with
our current sources in
ftp://ftp.denx.de/pub/LinuxPPC/usr/src/linux-2.4.3-pre3-2001-03-11.tar.bz2
Short summary of the new features:
* support for up to 6 serial ports on MPC860 systems
* MPC8xx watchdog support (need appropriate support in the firmware
which is available with PPCBoot)
* IP860 VMEBus memory support
* IP860 VMEBus interrupt support
* IP860 Real-Time Clock support
* Status LED driver
* AMD flash chip support
* INTEL flash chip support
* Allow passing a "mem=XXX" boot argument
* fix softemu8xx.o linkage
* "embedded IDE" support (IDE drives connected directly to the 8xx
PCMCIA port, and for real PCCARD interfaces like CompactFlash or
harddisk adapter cards, but without need for the full PCMCIA
package; also usable for boot devices).
Best regards,
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
Perfection is reached, not when there is no longer anything to add,
but when there is no longer anything to take away.
- Antoine de Saint-Exupery
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
^ permalink raw reply [flat|nested] 5+ messages in thread
* RE: Wolfgang's updates
@ 2001-03-13 9:49 Kári Davíðsson
2001-03-13 14:30 ` Wolfgang Denk
0 siblings, 1 reply; 5+ messages in thread
From: Kári Davíðsson @ 2001-03-13 9:49 UTC (permalink / raw)
To: linuxppc-dev
> -----Original Message-----
> From: Wolfgang Denk [mailto:wd@denx.de]
> Sent: 12. mars 2001 21:58
> To: Dan Malek; Tom Rini
> Cc: linuxppc-dev@lists.linuxppc.org
> Subject: Re: Wolfgang's updates
[SNIP]
> Ummm... The flash stuff is just adding NEW files. The fact they have
> been tested on PPC only should not create a problem adding the files.
> Many people add x86 drivers that don't work on PPC ;-)
[SNIP]
> * AMD flash chip support
> * INTEL flash chip support
[SNIP]
> PCMCIA port, and for real PCCARD interfaces like CompactFlash or
> harddisk adapter cards, but without need for the full PCMCIA
> package; also usable for boot devices).
>
Isn't this exactly what mtd is dooing, i.e. generating a general
interface to flash devices.
Isn't this a duplication of work, and deemed to be rejected from the
official kernel because the mtd is allready in the official kernel?
K.D.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Wolfgang's updates
2001-03-13 9:49 Kári Davíðsson
@ 2001-03-13 14:30 ` Wolfgang Denk
0 siblings, 0 replies; 5+ messages in thread
From: Wolfgang Denk @ 2001-03-13 14:30 UTC (permalink / raw)
To: Kári Davíðsson; +Cc: linuxppc-dev
In message <EADB10BAC266A14A85ECBF8686A73E3108AFC4@kolkrabbi.flaga.is> you wrote:
>
> > * AMD flash chip support
> > * INTEL flash chip support
...
> > PCMCIA port, and for real PCCARD interfaces like CompactFlash or
> > harddisk adapter cards, but without need for the full PCMCIA
> > package; also usable for boot devices).
...
> Isn't this exactly what mtd is dooing, i.e. generating a general
> interface to flash devices.
It's not a general interface, just an ordinary character device
driver.
Yes, you probably can replace it by MTD, and this is what we
eventually plan for the future. But our flash driver pre-dates MTD by
som time, and has been around since 2.2.5 or so. It is used by
several of our customers, and we will have to maintain it for some
time anyway.
And I don't really see a problem with having two independend
solutions for similar problems.
For instance, so far MTD does not even compile for CFI conformant
flash chips; last time I tried I got this:
cfi_cmdset_0002.c:304: #error not support big endian yet
The other patch to enable IDE devices like harddisks or CompactFlash
as boot devices using the PCMCIA port of the MPC8xx is - AFAIK -
something that is not even addressed by MTD. Nor was there any other
working solution for it.
> Isn't this a duplication of work, and deemed to be rejected from the
> official kernel because the mtd is allready in the official kernel?
Even with MTD - why generally reject an alternative solution? For
instance, we have several types of filesystems, too.
The "one size fits all" method does not apply to embedded devices,
and that's what I have in mind.
If you don't like it, you don't have to use it. It does not hurt you.
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
In C we had to code our own bugs, in C++ we can inherit them.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
^ permalink raw reply [flat|nested] 5+ messages in thread
* RE: Wolfgang's updates
@ 2001-03-13 15:03 Kári Davíðsson
0 siblings, 0 replies; 5+ messages in thread
From: Kári Davíðsson @ 2001-03-13 15:03 UTC (permalink / raw)
To: linuxppc-dev
> -----Original Message-----
> From: Wolfgang Denk [mailto:wd@denx.de]
> Sent: 13. mars 2001 14:31
> To: Kári Davíðsson
> Cc: linuxppc-dev@lists.linuxppc.org
> Subject: Re: Wolfgang's updates
>
>
> In message
> <EADB10BAC266A14A85ECBF8686A73E3108AFC4@kolkrabbi.flaga.is> you wrote:
> >
> > > * AMD flash chip support
> > > * INTEL flash chip support
> ...
> > > PCMCIA port, and for real PCCARD interfaces like CompactFlash or
> > > harddisk adapter cards, but without need for the full PCMCIA
> > > package; also usable for boot devices).
> ...
> > Isn't this exactly what mtd is dooing, i.e. generating a general
> > interface to flash devices.
>
> It's not a general interface, just an ordinary character device
> driver.
One of the interfaces that mtd implements is a character interface.
>
> Yes, you probably can replace it by MTD, and this is what we
> eventually plan for the future. But our flash driver pre-dates MTD by
Great.
> som time, and has been around since 2.2.5 or so. It is used by
I know. I was using it with the 2.2.5. and made it work with the
AM29LV160BT
although I am not shure if the pathces ware ever used by anyone except
me.
> several of our customers, and we will have to maintain it for some
> time anyway.
>
> And I don't really see a problem with having two independend
> solutions for similar problems.
Well I was just saying that Linus has rejected patches before because
the
problem was allready solved (in a diffrent way maybe) elsewhere.
(For example ggi v.s. X11, devfs in busybox v.s. /proc and probably a
lot more)
>
> For instance, so far MTD does not even compile for CFI conformant
> flash chips; last time I tried I got this:
>
> cfi_cmdset_0002.c:304: #error not support big endian yet
The resent snapshots of the mtd system works for me, i.e. the character
device part.
Thats on an mpc823e with one Intel TE28F320 flash chip on a 2.4.x
kernel.
Although I have not tried to put a filesystem on it yet, I don't
foreseeing it as becoming
a big problem, since the low level driver seem to work (fingers crossed
8-) ).
>
> The other patch to enable IDE devices like harddisks or CompactFlash
> as boot devices using the PCMCIA port of the MPC8xx is - AFAIK -
> something that is not even addressed by MTD. Nor was there any other
> working solution for it.
>
> > Isn't this a duplication of work, and deemed to be rejected from the
> > official kernel because the mtd is allready in the official kernel?
>
> Even with MTD - why generally reject an alternative solution? For
> instance, we have several types of filesystems, too.
Well, like I said before it has happened. The reason probably beeing, it
is easier to maintain in the long run.
>
> The "one size fits all" method does not apply to embedded devices,
> and that's what I have in mind.
But still we are all trying to make "one fit all", i.e. the Linux
kernel,
and that is what I have in mind.
>
> If you don't like it, you don't have to use it. It does not hurt you.
Of course.
>
> Wolfgang Denk
>
> --
> Software Engineering: Embedded and Realtime Systems, Embedded Linux
> Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
> In C we had to code our own bugs, in C++ we can inherit them.
>
Regards,
K.D.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
^ permalink raw reply [flat|nested] 5+ messages in thread
* Wolfgang's updates
@ 2006-03-02 13:20 Tony
0 siblings, 0 replies; 5+ messages in thread
From: Tony @ 2006-03-02 13:20 UTC (permalink / raw)
To: linuxppc-dev
[-- Attachment #1: Type: text/plain, Size: 178 bytes --]
Dear Mr.WolfGang,
Can u do me a favor,I need U_boot 1.1.4, I am trying to download it from internet,but I am failed! I am very appreciate your help!thx!
your Tony
[-- Attachment #2: Type: text/html, Size: 718 bytes --]
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2006-03-02 13:27 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-03-02 13:20 Wolfgang's updates Tony
-- strict thread matches above, loose matches on Subject: below --
2001-03-13 15:03 Kári Davíðsson
2001-03-13 9:49 Kári Davíðsson
2001-03-13 14:30 ` Wolfgang Denk
[not found] <3A9EEB84.63C6412@mvista.com>
2001-03-12 21:57 ` Wolfgang Denk
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).