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/tsunami_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/tsunami_pci.c')
| -rw-r--r-- | sys/alpha/pci/tsunami_pci.c | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/sys/alpha/pci/tsunami_pci.c b/sys/alpha/pci/tsunami_pci.c index ebf8855..cd392e1 100644 --- a/sys/alpha/pci/tsunami_pci.c +++ b/sys/alpha/pci/tsunami_pci.c @@ -224,8 +224,10 @@ tsunami_pcib_read_config(device_t dev, int b, int s, int f, switch (width) { case 1: CFGREAD(h, b, s, f, reg, ldbu, 1, u_int8_t); + break; case 2: CFGREAD(h, b, s, f, reg, ldwu, 2, u_int16_t); + break; case 4: CFGREAD(h, b, s, f, reg, ldl, 4, u_int32_t); } @@ -240,8 +242,10 @@ tsunami_pcib_write_config(device_t dev, int b, int s, int f, switch (width) { case 1: CFGWRITE(h, b, s, f, reg, val, stb, 1); + break; case 2: CFGWRITE(h, b, s, f, reg, val, stw, 2); + break; case 4: CFGWRITE(h, b, s, f, reg, val, stl, 4); } |
