<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN" "http://www.w3.org/TR/REC-html40/strict.dtd"><html><head><meta name="qrichtext" content="1" /><style type="text/css">p, li { white-space: pre-wrap; }</style></head><body style=" font-family:'Arial'; font-size:10pt; font-weight:400; font-style:normal;">Before you ran "make oldconfig" did you copy an existing kernel config to the kernel source directory and name it ".config"?<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>Shawn<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>On Friday 15 May 2009 05:47:28 pm David L. Willson wrote:<br>
> It's a DOD project. Running in a VM is not an option. Worse yet, the top priority is that the serial port must work. The ~serial~ port? What? I don't even know what to use one for, anymore, much less test it in Linux.<br>
> <br>
> Anyone got a clue for me on how to figure out which hardware is being supported by which module and vice-versa?<br>
> <br>
> And, when doing a "make oldconfig" the default for all new options is "(NEW)". Does that mean that choosing new causes me to choose the default answer for the new option? Or does "(NEW)" map to "no" or does it mean something else?<br>
> <br>
> David L. Willson<br>
> Trainer, Engineer, Enthusiast<br>
> MCT, MCSE, Linux+<br>
> tel://720.333.LANS<br>
> <br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p></body></html>