This is the mail archive of the binutils@sourceware.org mailing list for the binutils project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Coldfire control registers


Looking at the mcfv4e control registers in gas/config/tc-m68k.c I see

static const enum m68k_register mcfv4e_ctrl[] = {
  CACR, TC, ITT0, ITT1, DTT0, DTT1, BUSCR, VBR, PC, ROMBAR,
  ROMBAR1, RAMBAR0, RAMBAR1, MPCR, EDRAMBAR, SECMBAR, MBAR, MBAR0, MBAR1,
  PCR1U0, PCR1L0, PCR1U1, PCR1L1, PCR2U0, PCR2L0, PCR2U1, PCR2L1,
  PCR3U0, PCR3L0, PCR3U1, PCR3L1,
  0
};

this omits some ColdFire names (ASID, ACR0..3, MMUBAR), which are easy to fix. What puzzles me is that I can find no ColdFire documentation that mentions the 5475 and 5485 families as having
ROMBAR, ROMBAR1, MPCR, EDRAMBAR, SECMBAR, MBAR0, MBAR1,
PCR1U0, PCR1L0, PCR1U1, PCR1L1, PCR2U0, PCR2L0, PCR2U1, PCR2L1,
PCR3U0, PCR3L0, PCR3U1, PCR3L1,


In fact I don't know what chips have
  MPCR, EDRAMBAR, SECMBAR,
  PCR1U0, PCR1L0, PCR1U1, PCR1L1, PCR2U0, PCR2L0, PCR2U1, PCR2L1,
  PCR3U0, PCR3L0, PCR3U1, PCR3L1,

Grepping the changelog doesn't tell me when mcfv4e_control_regs got added, so I'm a little stumped.

My inclination is to add the ColdFire specific names, leave the m68k legacy names and remove the ones that are not supported.

nathan
--
Nathan Sidwell    ::   http://www.codesourcery.com   ::         CodeSourcery
nathan@codesourcery.com    ::     http://www.planetfall.pwp.blueyonder.co.uk


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]