[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#225622: excluding pcmcia resource ranges



Per Olofsson wrote:
> There is a [1]list in the PCMCIA HOWTO which lists settings for many
> computers. I was thinking of making a debconf dialogue with the
> settings in that list, but it would probably be better to implement
> your suggestion first. The list, however, can be of some help here.

That would certianly be easier to use, if less generic.

> >  - It's probably too complex for now to really operate on ranges as
> >    ranges; easier to operate on them as words that we either add or
> >    take away.
> 
> You mean by removing earlier statements in the file?

I was thinking that it would be overkill to support splitting a range by
excluding some bit in the middle of it.

> Presenting a list of computer models with special settings would be
> more user friendly, but could only be done in expert mode. It also
> can't be passed as boot time argument.

Sure it can. You'd have to get the model text exactly right though, so
nobody would want to do that..

> > Then we can add something to the syslinux boot help documentating that
> > for dell inspirons, the user needs to enter:
> 
> We can probably take the whole list from the howto.

How long is a the list, syslinux help space is limited.

Another approach would be to have a pcmcia/broken=yes boot setting, that
made it ask the questions with debconf. Or just require expert mode..

> > This assumes that all needed configuration can be done by appending
> > lines to config.opts, that might override earlier lines in the file
> > (excluding included ranges, including excluded ports, etc). I don't know
> > if that's true.
> 
> Looking at the source code, it appears so. But I haven't tested. Could
> you perhaps test it on your laptop?

Apparently one of your pcmcia-cs uploads, or the kernel upgrades have
fixed this problem, I can no longer reproduce pcmcia problems with that
laptop. Sucks to be me. ;-)


One other idea I had is that it would be marginally simpler if the
user's inpt was in the form: "exclude foo bar, exclude foo bar, include
foob bar. Then we need do no parsing, just echo the whole line. pcmcia(5)
seems to indicate that multiple statements on one line separate by
commas are legal.

-- 
see shy jo

Attachment: signature.asc
Description: Digital signature


Reply to: