Modify

Opened 7 years ago

Closed 7 years ago

Last modified 3 years ago

#7095 closed defect (fixed)

2.6.32 AR7 build doesn't initialise console correctly

Reported by: matt-openwrt@… Owned by: florian
Priority: normal Milestone: Barrier Breaker 14.07
Component: packages Version: Trunk
Keywords: Cc:

Description

Building 2.6.32 for AR7 builds the original 2.6.32 version of arch/mips/ar7/platform.c which includes:

uart_port[0].type = PORT_16550A;

...

uart_port[0].iotype = UPIO_MEM32;

...
These are incorrect; the file trunk/target/linux/ar7/files-2.6.30/arch/mips/ar7/platform.c does include the correct init code (type = PORT_AR7 and iotype = UPIO_MEM) but is only applied to 2.6.30 builds.

Attachments (0)

Change History (5)

comment:1 Changed 7 years ago by florian

  • Owner changed from developers to florian
  • Status changed from new to accepted

Why are they incorrect? UPIO_MEM32 means that it can use 32-bits wide accessors on the UART registers instead of byte-wide accessors.

comment:2 Changed 7 years ago by matt-openwrt@…

Hi Florian, sorry for the delay in getting back to you. I've only just had a chance to test it out; that UPIO_MEM32 was a red herring, left in from previous play. The real fix is just to have type = PORT_AR7 for both ports. My DSL502T has big problems without (i.e. console corruption & IRQ error spew ("too much work on irq 15")) and this change makes it work perfectly. It's a TI AR7 (TNETD7300), ID: 0x0005, Revision: 0x02. Cheers!

comment:3 Changed 7 years ago by florian

Ok, will check what is wrong with PORT_16550.

comment:4 Changed 7 years ago by florian

  • Resolution set to fixed
  • Status changed from accepted to closed

Fixed with r21457.

comment:5 Changed 3 years ago by jow

  • Milestone changed from Attitude Adjustment 12.09 to Barrier Breaker 14.07

Milestone Attitude Adjustment 12.09 deleted

Add Comment

Modify Ticket

Action
as closed .
The resolution will be deleted. Next status will be 'reopened'.
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.