Grant, Anton,
[snip]
> >
> > Doing this in parallel will speed things up significantly.
>
> Yeah; Then I would handle it as a separate cs# and map it to enabling
> multiple CS lines at a time.
sounds reasonable - will do it that way.
>
> > BTW: would "drivers/misc" be a proper location ?
> >
Grant,
[snip]
> >
> > 1.
> > The SC18IS602 is capable of generating interrupts which is *extremely*
> > useful triggering on the end of the actual SPI transaction and not the
> > end of I2C chip access. Since we need an IRQ_ACK over I2C (which takes
> > lng with IRQ being still asserted) I'm
Grant, Anton,
>
> There is no longer any need for separate of and non-of drivers for the same
> hardware. Any device may have the of_node pointer in struct device set, and
> drivers can use the pointer as an alternative to platform_data to get
> information about the hardware configuration.
Anton,
looks like I should have looked at include/spi/spi.h earlier :
/*
* INTERFACES between SPI master-side drivers and SPI infrastructure.
* (There's no SPI slave support for Linux yet...)
*/
...this is what I've been looking for.
thanks for your help and sorry for the noise.
Regards,
sent the created SPI bus ?
Is the (possibly) required driver (of_sc18is60x_spi ?) supposed to be an
I2C slave or an SPI host driver ?
Any help is welcome.
--
Mit freundlichen Grüßen / Best regards
André Schwarz
___
MATRIX VISION GmbH
- Entwi
Timur Tabi wrote:
Trent Piepho wrote:
Seems like it should keep the clock registers at what u-boot set them too.
Or we could have U-Boot put the i2c clock frequency into the I2C node, and let
the driver program the hardware again. That would keep the ugliness in U-Boot.
Wouldn't
Grant,
thanks for the quick feedback - I'll try to improve.
Hopefully monday morning will be on time
Comments inline.
regards,
André
Grant Likely wrote:
On Fri, Jul 04, 2008 at 06:35:39PM +0200, Andre Schwarz wrote:
The mvBlueCOUGAR-P is a MPC5200B based camera system with Intel Giga
Scott,
thanks for your reply.
Honestly I don't think the board wiring is incorrect.
FPGA goes to IRQ0 and miniPCI is wired to IRQ1.
Maybe there's a crosstalk problem since the pull-up resistors are
packaged inside an array ... I'll check this.
regards,
André
Scott Wood
Segher,
actually I'm the hardware designer ... :-) having trouble with
software.
The outputs are open-drain and can be connected (wired-or) together.
Otherwise "shared irq" wouldn't be possible that easy.
cheers,
André
Segher Boessenkool wrote:
interrupt-map = <0x5800 0 0 1 &ipic 0
Scott,
actually I'm having trouble with my PCI interrupts.
We are running 2.6.26-rc6 on a MPC8343 based board.
There are two external PCI devices connected (FPGA + miniPCI socket).
The FPGA is working fine and uses IRQ0 for its PCI_INTA line.
As soon there's a miniPCI module present and the dri
Fabio,
I'm running on a MPC8343.
The SD-Card is connected on the spi hardware controller.
regards,
André
Fabio Tosetto schrieb:
Hello,
I am trying to enable the SD over SPI on a emebedded system with one
processor powerpc mpc5200b; you have enabled mmc over spi into a native
spi or psc spi?
Anton,
we've just built a digital GigEVision camera based on a MPC8343 running
at 266/400 csb/core speed.
Transmission is done from a kernel module that allocates skb into which
the image data is DMA'd by an external PCI master.
As soon as the image data is complete all buffers are sent out v
Issue solved !
IRQ has been requested with IRQF_SHARED.
Obviously this is not neccessary and caused this bogus behaviour.
Don't know if it's a bug or a feature.
Cheers,
André
Andre Schwarz schrieb:
All,
actually I'm having trouble getting the IRQ0 work on a MPC8343 with
2.6.25-rc8.
There's
Michael Ellerman schrieb:
On Tue, 2008-04-22 at 12:23 -0500, Scott Wood wrote:
On Tue, Apr 22, 2008 at 06:58:33PM +0200, Andre Schwarz wrote:
I wonder if the IRQ number should match the vector of the datasheet ...
giving :
No. The numbers in /proc/interrupts are virtual IRQ numbers, which are
Scott,
thanks , but ... can't find "of_bus_ids[]" entry.
I'm obviously out of sync. My last git-pull from denx is 3 days old, now
- need to update on monday.
It seems hard for "normal" people to keep up these days !
Cheers,
André
Scott Wood wrote:
André Schw
Scott,
thanks for your help ... but
Scott Wood wrote:
On Fri, Apr 11, 2008 at 05:13:47PM +0200, Andre Schwarz wrote:
To me it looks like there's a problem regarding the local bus in general.
Am I missing a "compatible" or anything else ? "reg" or "ranges" ?
Do you have an of_bus_ids
Scott Wood wrote:
On Tue, Apr 08, 2008 at 03:50:26PM +0200, Andre Schwarz wrote:
after building a debug kernel and attaching the bdi2000 it looks like
the crash occurs during "console_init()" ...
Does your device tree have a /chosen node after u-boot is done with it?
find_legacy_seri
r difference is the CPU (MPC8343B), 512MB RAM (using 2 BATs of
course) and nothing else on the local bus besides the Nor-Flash.
Of course the MPC8343 has only a single PCI-32 and only one USB.
Do you have any hints on this ?
Do you suggest to wait for the 2.6.25 release ?
Do you know of any MPC8343
David Gibson schrieb:
On Thu, Mar 20, 2008 at 08:48:42AM +0100, André Schwarz wrote:
David Gibson schrieb:
On Thu, Mar 20, 2008 at 01:14:45AM +0100, Wolfgang Denk wrote:
In message <[EMAIL PROTECTED]> you wrote:
I've pulled the latest git and built a mpc5200_simple system with a
t;0" should be default.
-->"./dtc -I dts -O dtb -o /mnt/tftpboot/mvbc.dtb -S 8192 dts/mvbc.dts"
The system is running fine (please see discussions with Grant).
regards,
André Schwarz
MATRIX VISION GmbH, Talstraße 16, DE-71570 Oppenweiler - Registergericht:
Amtsgericht St
Grant Likely wrote:
On Sun, Mar 16, 2008 at 1:15 PM, André Schwarz
<[EMAIL PROTECTED]> wrote:
All,
I'm quite stuck in getting our MPC5200B based systems work on 2.6.24+
... maybe someone could give me some hints.
Up to now the systems have been running on 2.6.19 without a
dvanced" features like mtd partitions. All I want to get
working is the serial console on "/dev/ttyPSC0".
Are there any hidden stumbling blocks ?
Sorry for the "simple" questions but obviously there are many questions
coming up during move from "ppc" to
22 matches
Mail list logo
