diff options
| author | gallatin <gallatin@FreeBSD.org> | 2000-08-31 16:19:27 +0000 |
|---|---|---|
| committer | gallatin <gallatin@FreeBSD.org> | 2000-08-31 16:19:27 +0000 |
| commit | 10142f72b778cc949625c44837e2c84d41f5f030 (patch) | |
| tree | 356b59a92797a26684e5bddd2da908b7e7547f86 /sys/alpha/pci/t2_pci.c | |
| parent | c7b18640f73d1506099681f39168ca0e94146d46 (diff) | |
| download | FreeBSD-src-10142f72b778cc949625c44837e2c84d41f5f030.zip FreeBSD-src-10142f72b778cc949625c44837e2c84d41f5f030.tar.gz | |
Introduce explicit break statements in the various chipsets'
foo_pcib_[read|write]_config() functions rather than relying on
a break or return being in the CFG macro.
This fixes a panic later in the boot process on a UP1000. From
inspection, it looks like this fixes a similar problem in the tsunami code.
Approved by: dfr
Diffstat (limited to 'sys/alpha/pci/t2_pci.c')
| -rw-r--r-- | sys/alpha/pci/t2_pci.c | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/sys/alpha/pci/t2_pci.c b/sys/alpha/pci/t2_pci.c index 5d3eb21..687aa17 100644 --- a/sys/alpha/pci/t2_pci.c +++ b/sys/alpha/pci/t2_pci.c @@ -142,8 +142,10 @@ t2_pcib_read_config(device_t dev, int b, int s, int f, switch (width) { case 1: SWIZ_CFGREAD(b, s, f, reg, BYTE, u_int8_t); + break; case 2: SWIZ_CFGREAD(b, s, f, reg, WORD, u_int16_t); + break; case 4: SWIZ_CFGREAD(b, s, f, reg, LONG, u_int32_t); } @@ -157,8 +159,10 @@ t2_pcib_write_config(device_t dev, int b, int s, int f, switch (width) { case 1: SWIZ_CFGWRITE(b, s, f, reg, val, BYTE, u_int8_t); + break; case 2: SWIZ_CFGWRITE(b, s, f, reg, val, WORD, u_int16_t); + break; case 4: SWIZ_CFGWRITE(b, s, f, reg, val, LONG, u_int32_t); } |
