has fixed the speed mismatch, and I've verified that
schedule_timeout(HZ/10) produces a 100 millisecond delay. However, my
serial ports (brgs) are hosed.
-Alan
On 11/29/07, Alan Bennett <[EMAIL PROTECTED]> wrote:
> My uboot is new-ish, but I don't have the fdt commands? U
ree/cpus/PowerPC,[EMAIL PROTECTED]/i-cache-size
000 4000
On 11/29/07, Vitaly Bordug <[EMAIL PROTECTED]> wrote:
> On Wed, 28 Nov 2007 21:06:36 -0700
> Alan Bennett wrote:
>
> > It comes from uboot. Can you point me in the right direction to make
> > sure its
-cache-line-size = ;
d-cache-size = ;
i-cache-size = ;
timebase-frequency = <0>;
clock-frequency = <0>;
};
On 11/28/07, Scott Wood <[EMAIL PROTECTED]> wrote:
> Alan Bennett wro
I've got a routine that needs to delay for X microseconds, this is a
must. The command after schedule_timeout must has to wait for the HW
to complete a task that takes X microseconds.
I would think that one way to do this is with a simple
schedule_timeout. But in the example below, the time that
I'm working to adapt some work by Jochen Friedrich to support CPM2 i2c
devices. It appears I have the bus loaded and think I am configuring
it properly, but my results tell me different. I see no messages when
I attach a i2c monitor after u-boot loads.
Can anyone spot what is going wrong based o
Hello;
While working on i2c support, I've decided to update to a new kernel. In
the process of doing this, I'm not sure I've properly configured the MURAM
node to my device tree (i.e. serial is broken again). Also, does this, in
any way, change the way I offset the early debug transmit descrip
AIL PROTECTED]> wrote:
>
> The patch is orthogonal to your issue.
>
> There is NOT a driver in the kernel tree for the i2c on CPM2 based
> parts like the 8248 (from what I can tell).
>
> - k
>
> On Nov 14, 2007, at 9:31 AM, Alan Bennett wrote:
>
> > Does this patch
Does this patch support the cpm2 as well?
I get conflicting thoughts looking over the latest postings.
-Alan
On 11/13/07, Jon Smirl <[EMAIL PROTECTED]> wrote:
>
> I am working on a patch for i2c and device tree. I attached the current
> version.
>
> DTC entry looks like this.
>
>
I've got four devices on i2c that I need to read. Simple thermal and
voltage monitors. I2c works fine in uboot, and now I'm trying to get things
to work in linux.
In the kernel .config I enable
I2C
and
I2C_MPC
During the platform boot code:
I init the IO ports for i2c, (same as ep8248e code
Well, now that I've got IRQs requestable, I'm back to battling SCC1 / SCC4
initialization,
I've verified the iop structures, and things look set-up correctly.
/* SCC1 */
{2, 14, CPM_PIN_INPUT | CPM_PIN_PRIMARY},
{2, 15, CPM_PIN_INPUT | CPM_PIN_PRIMARY},
{3, 29, CPM_PIN_OUTPUT | CPM
Ok, so what does it take to expose an interrupt vector on a pq2 PIC??
-Alan
Current:
/
localbus{
...
fundevice1 {
interrupts = ;
interrupt-parent = <&PIC>;
};
...
[EMA
Freescale experts. Why on earth can't I request the IRQ for Timer1?
static int __init
dvr_ph_init(void)
{
u32 rv;
int k;
//rv = driver_register(&dvr_ph_driver);
for (k=0;k<64;k++) {
rv = request_irq(k,dvrph_isr , 0, "dvr_ph", NULL);
debian:
(on x86/fedora development system) (used on 82xx)
1. debootstrap with the --foreign
i.e. debootstrap --arch powerpc etch http://mirrors.kernel.org/debian
mannually create an inittab, create/copy some default /dev entries
2. boot 74xx target with above root filesystem, run
/debo
Need help adding new driver to supports a custom FPGA. Is there a
good driver that anyone would recommend I can look at that is fully
functional, works with 2.6.23 (powerpc style) and is described within
a device tree?
Bonus points:
uses freescale interrupts (timers/irq's from mpc 82xx/etc...)
We were developing with Linux 2.6.10 and a Planetcore boot loader,
however, recent work has us up and running with 2.6.23+ and U-boot
1.2.0. However, we are now running into a few challenges regarding
the differences.
Our driver writer's code isn't functioning, but it was with 2.6.10 and
planet c
alue:00010140
echo test > /dev/ttyCPM2 * note doesn't hang *
CPM uart[2]:startup - port->irq 002b
CPM uart[2]:startup - port->irq 43
cpm_setbrg:107 - brg:3 baud:9600
cpm_setbrg:108 - addr:e00119fc value:00010140
On 10/16/07, Scott Wood <[EMAIL PROTECTED]> wrote:
> Al
I'm using a modified ep8248e.dts to describe my hardware and I want to
enable the use of 3 standard interrupts.
1. irq5
2. timer1
3. timer2
How bad does this look?
soc --> cpm -->
timer {
device_type = "timer";
For some reason I'm unable to track down the right sequence to
initialize my serial ports. (note: my console is working, but
attempts to initialize SCC1 and SCC4 fail). My console has the luxury
of having uboot initialize it and its brg, but SCC1 / SCC4 aren't so
lucky.
A few questions: To us
Do you know what would cause this?
I've configured a board to console off of SMC1 (ttyCPM0) and on 1
board it works fine, however a new revision of the board I get the
following result and lose the console. Both boards have "exact"
versions of the kernel and u-boot.
BAD: console handover: boo
I added this to my boot/Makefile near the other mcpu=440 lines. I
believe there may be a fix coming?
$(obj)/treeboot-walnut.o: BOOTCFLAGS += -mcpu=440
$(obj)/4xx.o: BOOTCFLAGS += -mcpu=440
$(obj)/ebony.o: BOOTCFLAGS += -mcpu=440
On 9/24/07, Manil Gaouar <[EMAIL PROTECTED]> wrote:
> Hi there,
>
Device Tree and BRG?
The SMC1 uses BRG7 and the SCC1 uses BRG1, should we have both BRGs
configured in the .dts? ( BRG1 is configured).
Device Tree and Chosen?
Adding a chosen block and I end up off in the weeds. removing the
chosen block and I die within cpm_uart_console_write
chose
Ok, making progress on the ep8248 / devtrees, etc...
But I'm not getting any output on the serial and my log_buf is pretty
clean. Without console; what's the best way to figure out why I'm not
getting any output on my SMC1 serial port (using u-boot , not planetcore)?
-Alan
__log_buf:
Using Em
22 matches
Mail list logo
