> "Grant" == Grant Likely <[EMAIL PROTECTED]> writes:
Hi,
Grant> Rather than c67x00-hub.c being compiled seperately, the
Grant> original code had c67x00-hub.c *included* by c67x00-hcd.c.
Grant> This is a very bad idea. Simplest solution is to merge the
Grant> two files into one and be do
Hi,
can anybody send me the full patch for framebuffer driver?
thanks,
sherbin
___
Linuxppc-embedded mailing list
Linuxppc-embedded@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-embedded
Rather than c67x00-hub.c being compiled seperately, the original code had
c67x00-hub.c *included* by c67x00-hcd.c. This is a very bad idea.
Simplest solution is to merge the two files into one and be done with it.
Signed-off-by: Grant Likely <[EMAIL PROTECTED]>
---
drivers/usb/c67x00/c67x00-hcd.
Signed-off-by: Grant Likely <[EMAIL PROTECTED]>
---
drivers/usb/c67x00/c67x00-sched.c |8
1 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/usb/c67x00/c67x00-sched.c
b/drivers/usb/c67x00/c67x00-sched.c
index 0d08af7..3a870cf 100644
--- a/drivers/usb/c67x00/c67x00
Peter,
Here's the series of changes that I've made to the c67x00 driver. Most of
them are pretty straight forward. Most invasive is the rename of
'struct c67x00_drv' to 'struct c67x00_device' which is big and scary, but
doesn't really do much.
One thing that I haven't tackled is the layout of t
The structure describes per-device data, not per driver data. Convention
seems to be to use the _device suffix for this kind of structure.
Signed-off-by: Grant Likely <[EMAIL PROTECTED]>
---
drivers/usb/c67x00/c67x00-drv.c| 102 +++---
drivers/usb/c67x00/c67x00-drv.h| 10 +-
d
Fix up some of the error paths in the low level code to not go into an
endless loop. Replace the endless loops with failout code.
This patch is just a first step. It eliminates the endless loops, but
some of the code paths don't yet have a failure path, so instead the
driver uses BUG_ON() to die
Use the correct formulas and values for calculating the bittime within
a frame.
Signed-off-by: Grant Likely <[EMAIL PROTECTED]>
---
drivers/usb/c67x00/c67x00-hcd.h | 10 ++--
drivers/usb/c67x00/c67x00-sched.c | 42 +---
2 files changed, 45 insertions(+), 7
The active flag in a TD needs to be checked to determine whether or not
the TD was processed in the frame. Without this check, the HCD assumes
the TD completed successfully, when in reality it was not processed at all.
Signed-off-by: Grant Likely <[EMAIL PROTECTED]>
---
drivers/usb/c67x00/c67x00
On Tue, 12 Jun 2007, Domen Puncer wrote:
> Index: work-powerpc.git/include/asm-powerpc/mpc5200_rtc.h
> ===
> --- /dev/null
> +++ work-powerpc.git/include/asm-powerpc/mpc5200_rtc.h
> @@ -0,0 +1,49 @@
> +#ifndef _MPC5200_RTC_H_
> +#defi
In article <[EMAIL PROTECTED]> you write:
> On Thu, 24 May 2007, Andrei Konovalov wrote:
>
> > Hello,
> >
> > My Xilinx Virtex Development tree is now alive again.
> >
> > Please use the dev branch (master is just the ko copy):
> > http://source.mvista.com/git/gitweb.cgi?p=linux-xilinx-26.git;a=sh
On Saturday 09 June 2007, Andrei Konovalov wrote:
> The new patch is attached to this message.
Would you send a version that doesn't produce so many
warnings when run against scripts/checkpatch.pl ??
The issues seem to be mostly whitespace and linelength,
so that should be easy.
- Dave
_
Hi Laurent,
> I use a Linux 2.6.9 on a 85xx custom board with a NAND flash.
>
> This flash has some bad blocks.
> NAND device: Manufacturer ID: 0xec, Chip ID: 0xf1 (Samsung NAND 128MiB 3,3V
> 8-bit)
> Scanning device for bad blocks
> Bad eraseblock 8 at 0x0010
> Bad eraseblock 430 at 0x035c0
On Thu, 24 May 2007, Andrei Konovalov wrote:
> Hello,
>
> My Xilinx Virtex Development tree is now alive again.
>
> Please use the dev branch (master is just the ko copy):
> http://source.mvista.com/git/gitweb.cgi?p=linux-xilinx-26.git;a=shortlog;h=dev
I can not access the git-tree there: No such
Gary and Bill,
My need is to load a basic Linux kernel on boards to program multiple
NOR and NAND flashes with CRAMFS and JFFS2 (perhaps YAFFS) images.
I usually used mtd character accesses to do the job on NOR flashes.
But flash_eraseall and flashcp seem to be excellent tools.
I'll try them qu
Driver for internal rtc on mpc5200.
It isn't very useful, since its contents don't remain on
power off.
Can be used to set alarm for wake-up from deep-sleep or
one second periodic interrupt ;-)
Signed-off-by: Domen Puncer <[EMAIL PROTECTED]>
---
drivers/rtc/Kconfig | 10 +
drive
Driver for internal mpc5200 watchdog on general purpose timer 0.
For IPB clock of 132 MHz the maximum timeout is about 32 seconds.
Signed-off-by: Domen Puncer <[EMAIL PROTECTED]>
---
Hi!
I also have some generic GPT code that one could extend with
what he/she needs. Mail me if you'd find it use
17 matches
Mail list logo